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

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set

Linux · Linux

7.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 23 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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: As exposure requiresRemediation target: Within 365 days

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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.10-1Debian Security Tracker ↗Source updated 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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-43449 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-43449
155 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set dev->online_queues is a count incremented in nvme_init_queue. Thus, valid indices are 0 through dev->online_queues − 1. This patch fixes the loop condition to ensure the index stays within the valid range. Index 0 is excluded because it is the admin queue. KASAN splat: ================================================================== BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 Read of size 2 at addr ffff88800592a574 by task kworker/u8:5/74 CPU: 0 UID: 0 PID: 74 Comm: kworker/u8:5 Not tainted 6.19.0-dirty #10 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: nvme-reset-wq nvme_reset_work Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xea/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xce/0x5d0 mm/kasan/report.c:482 kasan_report+0xdc/0x110 mm/kasan/report.c:595 __asan_report_load2_noabort+0x18/0x20 mm/kasan/report_generic.c:379 nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 nvme_reset_work+0x36b/0x8c0 drivers/nvme/host/pci.c:3252 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 Allocated by task 34 on cpu 1 at 4.241550s: kasan_save_stack+0x2c/0x60 mm/kasan/common.c:57 kasan_save_track+0x1c/0x70 mm/kasan/common.c:78 kasan_save_alloc_info+0x3c/0x50 mm/kasan/generic.c:570 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0xb5/0xc0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __do_kmalloc_node mm/slub.c:5657 [inline] __kmalloc_node_noprof+0x2bf/0x8d0 mm/slub.c:5663 kmalloc_array_node_noprof include/linux/slab.h:1075 [inline] nvme_pci_alloc_dev drivers/nvme/host/pci.c:3479 [inline] nvme_probe+0x2f1/0x1820 drivers/nvme/host/pci.c:3534 local_pci_probe+0xef/0x1c0 drivers/pci/pci-driver.c:324 pci_call_probe drivers/pci/pci-driver.c:392 [inline] __pci_device_probe drivers/pci/pci-driver.c:417 [inline] pci_device_probe+0x743/0x920 drivers/pci/pci-driver.c:451 call_driver_probe drivers/base/dd.c:583 [inline] really_probe+0x29b/0xb70 drivers/base/dd.c:661 __driver_probe_device+0x3b0/0x4a0 drivers/base/dd.c:803 driver_probe_device+0x56/0x1f0 drivers/base/dd.c:833 __driver_attach_async_helper+0x155/0x340 drivers/base/dd.c:1159 async_run_entry_fn+0xa6/0x4b0 kernel/async.c:129 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 The buggy address belongs to the object at ffff88800592a000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 244 bytes to the right of allocated 1152-byte region [ffff88800592a000, ffff88800592a480) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5928 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0xfffffc0000040(head|node=0|zone=1|lastcpupid=0x1fffff) page_type: f5(slab) raw: 000fffffc0000040 ffff888001042000 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000080008 00000000f5000000 0000000000000000 head: 000fffffc0000040 ffff888001042000 00000 ---truncated---
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-28755

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. 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: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set dev->online_queues is a count incremented in nvme_init_queue. Thus, valid indices are 0 through dev->online_queues − 1. This patch fixes the loop condition to ensure the index stays within the valid range. Index 0 is excluded because it is the admin queue. KASAN splat: ================================================================== BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 Read of size 2 at addr ffff88800592a574 by task kworker/u8:5/74 CPU: 0 UID: 0 PID: 74 Comm: kworker/u8:5 Not tainted 6.19.0-dirty #10 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: nvme-reset-wq nvme_reset_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xea/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xce/0x5d0 mm/kasan/report.c:482 kasan_report+0xdc/0x110 mm/kasan/report.c:595 __asan_report_load2_noabort+0x18/0x20 mm/kasan/report_generic.c:379 nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 nvme_reset_work+0x36b/0x8c0 drivers/nvme/host/pci.c:3252 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 </TASK> Allocated by task 34 on cpu 1 at 4.241550s: kasan_save_stack+0x2c/0x60 mm/kasan/common.c:57 kasan_save_track+0x1c/0x70 mm/kasan/common.c:78 kasan_save_alloc_info+0x3c/0x50 mm/kasan/generic.c:570 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0xb5/0xc0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __do_kmalloc_node mm/slub.c:5657 [inline] __kmalloc_node_noprof+0x2bf/0x8d0 mm/slub.c:5663 kmalloc_array_node_noprof include/linux/slab.h:1075 [inline] nvme_pci_alloc_dev drivers/nvme/host/pci.c:3479 [inline] nvme_probe+0x2f1/0x1820 drivers/nvme/host/pci.c:3534 local_pci_probe+0xef/0x1c0 drivers/pci/pci-driver.c:324 pci_call_probe drivers/pci/pci-driver.c:392 [inline] __pci_device_probe drivers/pci/pci-driver.c:417 [inline] pci_device_probe+0x743/0x920 drivers/pci/pci-driver.c:451 call_driver_probe drivers/base/dd.c:583 [inline] really_probe+0x29b/0xb70 drivers/base/dd.c:661 __driver_probe_device+0x3b0/0x4a0 drivers/base/dd.c:803 driver_probe_device+0x56/0x1f0 drivers/base/dd.c:833 __driver_attach_async_helper+0x155/0x340 drivers/base/dd.c:1159 async_run_entry_fn+0xa6/0x4b0 kernel/async.c:129 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 The buggy address belongs to the object at ffff88800592a000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 244 bytes to the right of allocated 1152-byte region [ffff88800592a000, ffff88800592a480) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5928 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0xfffffc0000040(head|node=0|zone=1|lastcpupid=0x1fffff) page_type: f5(slab) raw: 000fffffc0000040 ffff888001042000 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000080008 00000000f5000000 0000000000000000 head: 000fffffc0000040 ffff888001042000 00000 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set dev->online_queues is a count incremented in nvme_init_queue. Thus, valid indices are 0 through dev->online_queues − 1. This patch fixes the loop condition to ensure the index stays within the valid range. Index 0 is excluded because it is the admin queue. KASAN splat: ================================================================== BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 Read of size 2 at addr ffff88800592a574 by task kworker/u8:5/74 CPU: 0 UID: 0 PID: 74 Comm: kworker/u8:5 Not tainted 6.19.0-dirty #10 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: nvme-reset-wq nvme_reset_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xea/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xce/0x5d0 mm/kasan/report.c:482 kasan_report+0xdc/0x110 mm/kasan/report.c:595 __asan_report_load2_noabort+0x18/0x20 mm/kasan/report_generic.c:379 nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 nvme_reset_work+0x36b/0x8c0 drivers/nvme/host/pci.c:3252 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 </TASK> Allocated by task 34 on cpu 1 at 4.241550s: kasan_save_stack+0x2c/0x60 mm/kasan/common.c:57 kasan_save_track+0x1c/0x70 mm/kasan/common.c:78 kasan_save_alloc_info+0x3c/0x50 mm/kasan/generic.c:570 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0xb5/0xc0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __do_kmalloc_node mm/slub.c:5657 [inline] __kmalloc_node_noprof+0x2bf/0x8d0 mm/slub.c:5663 kmalloc_array_node_noprof include/linux/slab.h:1075 [inline] nvme_pci_alloc_dev drivers/nvme/host/pci.c:3479 [inline] nvme_probe+0x2f1/0x1820 drivers/nvme/host/pci.c:3534 local_pci_probe+0xef/0x1c0 drivers/pci/pci-driver.c:324 pci_call_probe drivers/pci/pci-driver.c:392 [inline] __pci_device_probe drivers/pci/pci-driver.c:417 [inline] pci_device_probe+0x743/0x920 drivers/pci/pci-driver.c:451 call_driver_probe drivers/base/dd.c:583 [inline] really_probe+0x29b/0xb70 drivers/base/dd.c:661 __driver_probe_device+0x3b0/0x4a0 drivers/base/dd.c:803 driver_probe_device+0x56/0x1f0 drivers/base/dd.c:833 __driver_attach_async_helper+0x155/0x340 drivers/base/dd.c:1159 async_run_entry_fn+0xa6/0x4b0 kernel/async.c:129 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 The buggy address belongs to the object at ffff88800592a000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 244 bytes to the right of allocated 1152-byte region [ffff88800592a000, ffff88800592a480) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5928 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0xfffffc0000040(head|node=0|zone=1|lastcpupid=0x1fffff) page_type: f5(slab) raw: 000fffffc0000040 ffff888001042000 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000080008 00000000f5000000 0000000000000000 head: 000fffffc0000040 ffff888001042000 00000 ---truncated---

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set dev->online_queues is a count incremented in nvme_init_queue. Thus, valid indices are 0 through dev->online_queues − 1. This patch fixes the loop condition to ensure the index stays within the valid range. Index 0 is excluded because it is the admin queue. KASAN splat: ================================================================== BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] BUG: KASAN: slab-out-of-bounds in nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 Read of size 2 at addr ffff88800592a574 by task kworker/u8:5/74 CPU: 0 UID: 0 PID: 74 Comm: kworker/u8:5 Not tainted 6.19.0-dirty #10 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: nvme-reset-wq nvme_reset_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xea/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xce/0x5d0 mm/kasan/report.c:482 kasan_report+0xdc/0x110 mm/kasan/report.c:595 __asan_report_load2_noabort+0x18/0x20 mm/kasan/report_generic.c:379 nvme_dbbuf_free drivers/nvme/host/pci.c:377 [inline] nvme_dbbuf_set+0x39c/0x400 drivers/nvme/host/pci.c:404 nvme_reset_work+0x36b/0x8c0 drivers/nvme/host/pci.c:3252 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 </TASK> Allocated by task 34 on cpu 1 at 4.241550s: kasan_save_stack+0x2c/0x60 mm/kasan/common.c:57 kasan_save_track+0x1c/0x70 mm/kasan/common.c:78 kasan_save_alloc_info+0x3c/0x50 mm/kasan/generic.c:570 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0xb5/0xc0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __do_kmalloc_node mm/slub.c:5657 [inline] __kmalloc_node_noprof+0x2bf/0x8d0 mm/slub.c:5663 kmalloc_array_node_noprof include/linux/slab.h:1075 [inline] nvme_pci_alloc_dev drivers/nvme/host/pci.c:3479 [inline] nvme_probe+0x2f1/0x1820 drivers/nvme/host/pci.c:3534 local_pci_probe+0xef/0x1c0 drivers/pci/pci-driver.c:324 pci_call_probe drivers/pci/pci-driver.c:392 [inline] __pci_device_probe drivers/pci/pci-driver.c:417 [inline] pci_device_probe+0x743/0x920 drivers/pci/pci-driver.c:451 call_driver_probe drivers/base/dd.c:583 [inline] really_probe+0x29b/0xb70 drivers/base/dd.c:661 __driver_probe_device+0x3b0/0x4a0 drivers/base/dd.c:803 driver_probe_device+0x56/0x1f0 drivers/base/dd.c:833 __driver_attach_async_helper+0x155/0x340 drivers/base/dd.c:1159 async_run_entry_fn+0xa6/0x4b0 kernel/async.c:129 process_one_work+0x956/0x1aa0 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x65c/0xe60 kernel/workqueue.c:3421 kthread+0x41a/0x930 kernel/kthread.c:463 ret_from_fork+0x6f8/0x8c0 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 The buggy address belongs to the object at ffff88800592a000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 244 bytes to the right of allocated 1152-byte region [ffff88800592a000, ffff88800592a480) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5928 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0xfffffc0000040(head|node=0|zone=1|lastcpupid=0x1fffff) page_type: f5(slab) raw: 000fffffc0000040 ffff888001042000 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000080008 00000000f5000000 0000000000000000 head: 000fffffc0000040 ffff888001042000 00000 ---truncated---

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.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-125
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

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

d?id=CVE-2026-43425 Référence CVE CVE-2026-43426 https://www.cve.org/CVERecord?id=CVE-2026-43426 Référence CVE CVE-2026-43427 https://www.cve.org/CVERecord?id=CVE-2026-43427 Référence CVE CVE-2026-43428 https://www.cve.org/CVERecord?id=CVE-2026-43428 Référence CVE CVE-2026-43429 https://www.cve.org/CVERecord?id=CVE-2026-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43459 https://www.cve.org/CVERecord?id=CVE-2026-43459 Référence CVE CVE-2026-43466 https://www.cve.org/CVERecord?id=CVE-2026-43466 Référence CVE CVE-2026-43469 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-43425 Référence CVE CVE-2026-43426 https://www.cve.org/CVERecord?id=CVE-2026-43426 Référence CVE CVE-2026-43427 https://www.cve.org/CVERecord?id=CVE-2026-43427 Référence CVE CVE-2026-43428 https://www.cve.org/CVERecord?id=CVE-2026-43428 Référence CVE CVE-2026-43429 https://www.cve.org/CVERecord?id=CVE-2026-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43459 https://www.cve.org/CVERecord?id=CVE-2026-43459 Référence CVE CVE-2026-43465 https://www.cve.org/CVERecord?id=CVE-2026-43465 Référence CVE CVE-2026-43466 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-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43436 https://www.cve.org/CVERecord?id=CVE-2026-43436 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43441 https://www.cve.org/CVERecord?id=CVE-2026-43441 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43448 https://www.cve.org/CVERecord?id=CVE-2026-43448 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43455 https://www.cve.org/CVERecord?id=CVE-2026-43455 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43457 https://www.cve.org/CVERecord?id=CVE-2026-43457 Référence CVE CVE-2026-43458 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-2026-43309 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43370 https://www.cve.org/CVERecord?id=CVE-2026-43370 Référence CVE CVE-2026-43373 https://www.cve.org/CVERecord?id=CVE-2026-43373 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43425 https://www.cve.org/CVERecord?id=CVE-2026-43425 Référence CVE CVE-2026-43427 https://www.cve.org/CVERecord?id=CVE-2026-43427 Référence CVE CVE-2026-43440 https://www.cve.org/CVERecord?id=CVE-2026-43440 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43466 https://www.cve.org/CVERecord?id=CVE-2026-43466 Référence CVE CVE-2026-43475 https://www.cve.org/CVERecord?id=CVE-2026-43475 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-45857 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-43425 Référence CVE CVE-2026-43426 https://www.cve.org/CVERecord?id=CVE-2026-43426 Référence CVE CVE-2026-43427 https://www.cve.org/CVERecord?id=CVE-2026-43427 Référence CVE CVE-2026-43428 https://www.cve.org/CVERecord?id=CVE-2026-43428 Référence CVE CVE-2026-43429 https://www.cve.org/CVERecord?id=CVE-2026-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43459 https://www.cve.org/CVERecord?id=CVE-2026-43459 Référence CVE CVE-2026-43466 https://www.cve.org/CVERecord?id=CVE-2026-43466 Référence CVE CVE-2026-43469 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43384 Référence CVE CVE-2026-43386 https://www.cve.org/CVERecord?id=CVE-2026-43386 Référence CVE CVE-2026-43403 https://www.cve.org/CVERecord?id=CVE-2026-43403 Référence CVE CVE-2026-43405 https://www.cve.org/CVERecord?id=CVE-2026-43405 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43415 https://www.cve.org/CVERecord?id=CVE-2026-43415 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43457 https://www.cve.org/CVERecord?id=CVE-2026-43457 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43465 https://www.cve.org/CVERecord?id=CVE-2026-43465 Référence CVE CVE-2026-43466 https://www.cve.org/CVERecord?id=CVE-2026-43466 Référence CVE CVE-2026-43468 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-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43436 https://www.cve.org/CVERecord?id=CVE-2026-43436 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43441 https://www.cve.org/CVERecord?id=CVE-2026-43441 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43448 https://www.cve.org/CVERecord?id=CVE-2026-43448 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43455 https://www.cve.org/CVERecord?id=CVE-2026-43455 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43457 https://www.cve.org/CVERecord?id=CVE-2026-43457 Référence CVE CVE-2026-43458 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-43428 Référence CVE CVE-2026-43429 https://www.cve.org/CVERecord?id=CVE-2026-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43436 https://www.cve.org/CVERecord?id=CVE-2026-43436 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43443 https://www.cve.org/CVERecord?id=CVE-2026-43443 Référence CVE CVE-2026-43444 https://www.cve.org/CVERecord?id=CVE-2026-43444 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43457 https://www.cve.org/CVERecord?id=CVE-2026-43457 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43459 https://www.cve.org/CVERecord?id=CVE-2026-43459 Référence CVE CVE-2026-43465 https://www.cve.org/CVERecord?id=CVE-2026-43465 Référence CVE CVE-2026-43466 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-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43436 https://www.cve.org/CVERecord?id=CVE-2026-43436 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43441 https://www.cve.org/CVERecord?id=CVE-2026-43441 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43448 https://www.cve.org/CVERecord?id=CVE-2026-43448 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43455 https://www.cve.org/CVERecord?id=CVE-2026-43455 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43457 https://www.cve.org/CVERecord?id=CVE-2026-43457 Référence CVE CVE-2026-43458 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-43426 Référence CVE CVE-2026-43427 https://www.cve.org/CVERecord?id=CVE-2026-43427 Référence CVE CVE-2026-43428 https://www.cve.org/CVERecord?id=CVE-2026-43428 Référence CVE CVE-2026-43429 https://www.cve.org/CVERecord?id=CVE-2026-43429 Référence CVE CVE-2026-43430 https://www.cve.org/CVERecord?id=CVE-2026-43430 Référence CVE CVE-2026-43432 https://www.cve.org/CVERecord?id=CVE-2026-43432 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43445 https://www.cve.org/CVERecord?id=CVE-2026-43445 Référence CVE CVE-2026-43449 https://www.cve.org/CVERecord?id=CVE-2026-43449 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43459 https://www.cve.org/CVERecord?id=CVE-2026-43459 Référence CVE CVE-2026-43466 https://www.cve.org/CVERecord?id=CVE-2026-43466 Référence CVE CVE-2026-43472 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-016867LinuxのLinux Kernelにおける境界外読み取りに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。nvme-pciのnvme_dbbuf_set関数内で発生していたスラブ境界外アクセスの問題を修正しました。dev-online_queuesはnvme_init_queue関数内でインクリメントされるカウントであり、有効なインデックスは0からdev-online_queues−1までです。本パッチはループ条件を修正し、インデックスが有効範囲内に収まるようにしました。インデックス0は管理キューのため除外されています。KASANエラーの内容は、nvme_dbbuf_free関数の377行目とnvme_dbbuf_set関数の404行目でスラブ境界外アクセスが検出されたことです。サイズ2の読み込みがタスクkworker/u8:5によって行われました。問題のアドレスは、サイズ2048のkmalloc-2kキャッシュ内の領域[ffff88800592a000, ffff88800592a480)の1152バイト割り当て範囲の右244バイト外に位置していました。この問題はnvme_pciドライバのオンラインキュー管理におけるインデックス計算の不備によって発生しました。パッチにより正しい範囲チェックが追加され、不正アクセスが防止されました。

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: < 5.10, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.130 ≤ 6.6.*, 6.12.78 ≤ 6.12.*, 6.18.19 ≤ 6.18.*, 6.19.9 ≤ 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 8 May 2026 · Last source change 23 May 2026, 16:07 UTC · CWE-125 · Out-of-bounds Read

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-28755
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-28755↗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-43449 · cve.blacktree.nl