BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31510High confidence

Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-31510 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-31510
290 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb Before using sk pointer, check if it is null. Fix the following: KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267] CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025 Workqueue: events l2cap_info_timeout RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df b6 04 07 3c 08 0f 92 c0 c3 cc cce veth0_macvtap: entered promiscuous mode RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0 PKRU: 55555554 Call Trace: __kasan_check_byte+0x12/0x40 lock_acquire+0x79/0x2e0 lock_sock_nested+0x48/0x100 ? l2cap_sock_ready_cb+0x46/0x160 l2cap_sock_ready_cb+0x46/0x160 l2cap_conn_start+0x779/0xff0 ? __pfx_l2cap_conn_start+0x10/0x10 ? l2cap_info_timeout+0x60/0xa0 ? __pfx___mutex_lock+0x10/0x10 l2cap_info_timeout+0x68/0xa0 ? process_scheduled_works+0xa8d/0x18c0 process_scheduled_works+0xb6e/0x18c0 ? __pfx_process_scheduled_works+0x10/0x10 ? assign_work+0x3d5/0x5e0 worker_thread+0xa53/0xfc0 kthread+0x388/0x470 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x51e/0xb90 ? __pfx_ret_from_fork+0x10/0x10 veth1_macvtap: entered promiscuous mode ? __switch_to+0xc7d/0x1450 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 Modules linked in: ---[ end trace 0000000000000000 ]--- batman_adv: batadv0: Interface activated: batadv_slave_0 batman_adv: batadv0: Interface activated: batadv_slave_1 netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df b6 04 07 3c 08 0f 92 c0 c3 cc cce ieee80211 phy39: Selected rate control algorithm 'minstrel_ht' RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exception
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-24892

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb Before using sk pointer, check if it is null. Fix the following: KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267] CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025 Workqueue: events l2cap_info_timeout RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce veth0_macvtap: entered promiscuous mode RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0 PKRU: 55555554 Call Trace: <TASK> __kasan_check_byte+0x12/0x40 lock_acquire+0x79/0x2e0 lock_sock_nested+0x48/0x100 ? l2cap_sock_ready_cb+0x46/0x160 l2cap_sock_ready_cb+0x46/0x160 l2cap_conn_start+0x779/0xff0 ? __pfx_l2cap_conn_start+0x10/0x10 ? l2cap_info_timeout+0x60/0xa0 ? __pfx___mutex_lock+0x10/0x10 l2cap_info_timeout+0x68/0xa0 ? process_scheduled_works+0xa8d/0x18c0 process_scheduled_works+0xb6e/0x18c0 ? __pfx_process_scheduled_works+0x10/0x10 ? assign_work+0x3d5/0x5e0 worker_thread+0xa53/0xfc0 kthread+0x388/0x470 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x51e/0xb90 ? __pfx_ret_from_fork+0x10/0x10 veth1_macvtap: entered promiscuous mode ? __switch_to+0xc7d/0x1450 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- batman_adv: batadv0: Interface activated: batadv_slave_0 batman_adv: batadv0: Interface activated: batadv_slave_1 netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce ieee80211 phy39: Selected rate control algorithm 'minstrel_ht' RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exception

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb Before using sk pointer, check if it is null. Fix the following: KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267] CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025 Workqueue: events l2cap_info_timeout RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce veth0_macvtap: entered promiscuous mode RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0 PKRU: 55555554 Call Trace: <TASK> __kasan_check_byte+0x12/0x40 lock_acquire+0x79/0x2e0 lock_sock_nested+0x48/0x100 ? l2cap_sock_ready_cb+0x46/0x160 l2cap_sock_ready_cb+0x46/0x160 l2cap_conn_start+0x779/0xff0 ? __pfx_l2cap_conn_start+0x10/0x10 ? l2cap_info_timeout+0x60/0xa0 ? __pfx___mutex_lock+0x10/0x10 l2cap_info_timeout+0x68/0xa0 ? process_scheduled_works+0xa8d/0x18c0 process_scheduled_works+0xb6e/0x18c0 ? __pfx_process_scheduled_works+0x10/0x10 ? assign_work+0x3d5/0x5e0 worker_thread+0xa53/0xfc0 kthread+0x388/0x470 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x51e/0xb90 ? __pfx_ret_from_fork+0x10/0x10 veth1_macvtap: entered promiscuous mode ? __switch_to+0xc7d/0x1450 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- batman_adv: batadv0: Interface activated: batadv_slave_0 batman_adv: batadv0: Interface activated: batadv_slave_1 netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce ieee80211 phy39: Selected rate control algorithm 'minstrel_ht' RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exception

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb Before using sk pointer, check if it is null. Fix the following: KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267] CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025 Workqueue: events l2cap_info_timeout RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce veth0_macvtap: entered promiscuous mode RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0 PKRU: 55555554 Call Trace: <TASK> __kasan_check_byte+0x12/0x40 lock_acquire+0x79/0x2e0 lock_sock_nested+0x48/0x100 ? l2cap_sock_ready_cb+0x46/0x160 l2cap_sock_ready_cb+0x46/0x160 l2cap_conn_start+0x779/0xff0 ? __pfx_l2cap_conn_start+0x10/0x10 ? l2cap_info_timeout+0x60/0xa0 ? __pfx___mutex_lock+0x10/0x10 l2cap_info_timeout+0x68/0xa0 ? process_scheduled_works+0xa8d/0x18c0 process_scheduled_works+0xb6e/0x18c0 ? __pfx_process_scheduled_works+0x10/0x10 ? assign_work+0x3d5/0x5e0 worker_thread+0xa53/0xfc0 kthread+0x388/0x470 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x51e/0xb90 ? __pfx_ret_from_fork+0x10/0x10 veth1_macvtap: entered promiscuous mode ? __switch_to+0xc7d/0x1450 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- batman_adv: batadv0: Interface activated: batadv_slave_0 batman_adv: batadv0: Interface activated: batadv_slave_1 netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 RIP: 0010:kasan_byte_accessible+0x12/0x30 Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cce ieee80211 phy39: Selected rate control algorithm 'minstrel_ht' RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001 RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000 R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exception

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1252Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31489 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=CVE-2026-31494 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31489 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=CVE-2026-31494 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31501 https://www.cve.org/CVERecord?id=CVE-2026-31501 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31499 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31501 https://www.cve.org/CVERecord?id=CVE-2026-31501 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31489 https://www.cve.org/CVERecord?id=CVE-2026-31489 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31513 https://www.cve.org/CVERecord?id=CVE-2026-31513 Référence CVE CVE-2026-31514 https://www.cve.org/CVERecord?id=CVE-2026-31514 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-21710 Référence CVE CVE-2025-21953 https://www.cve.org/CVERecord?id=CVE-2025-21953 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31542 https://www.cve.org/CVERecord?id=CVE-2026-31542 Référence CVE CVE-2026-31598 https://www.cve.org/CVERecord?id=CVE-2026-31598 Référence CVE CVE-2026-31624 https://www.cve.org/CVERecord?id=CVE-2026-31624 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31485 Référence CVE CVE-2026-31489 https://www.cve.org/CVERecord?id=CVE-2026-31489 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=CVE-2026-31494 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31499 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31513 https://www.cve.org/CVERecord?id=CVE-2026-31513 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31499 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0696Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31485 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=CVE-2026-31494 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0547Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31495 Référence CVE CVE-2026-31496 https://www.cve.org/CVERecord?id=CVE-2026-31496 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-31500 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0519Multiples vulnérabilités dans Microsoft Azure Linux

sécurité Microsoft CVE-2026-31485 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31494 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31495 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31496 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31497 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31500 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31503 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31504 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31507 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31509 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31510 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31515 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31518 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31519 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31520 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31521 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31522 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31523 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31524 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31525 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31528 du 23 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-013258LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：BluetoothのL2CAPに関する問題で、l2cap_sock_ready_cb内のnullポインタ参照が修正されました。skポインタを使用する前にnullかどうかを必ず確認するようにしています。修正内容は次の通りです。KASANによりnullポインタ参照（範囲 [0x0000000000000260-0x0000000000000267]）が発生していた問題で、CPU: 0、UID: 0、PID: 5985のkworker/0:5で起きていました。QEMU標準PC（Q35 + ICH9、2009）環境において再現が確認されています。この問題はl2cap_sock_ready_cb関数および関連するロック取得処理に起因し、不正なポインタアクセスがカーネルパニックを引き起こしていました。修正によって、skポインタがnullの場合に適切にチェックを行うことで、これらのクラッシュを防止できるようになりました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.6, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.131 ≤ 6.6.*, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 22 Apr 2026 · Last source change 11 May 2026, 22:10 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-24892
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-24892↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-31510 · cve.blacktree.nl