CVE-2026-43449

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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---

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (8)

Auto-updated Jun 12, 2026
Patch available.
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d7990c936e25f484b61a5adeeadc1d290a9fd16e
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b4e78f1427c7d6859229ae9616df54e1fc05a516
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86183d550559e45e07059bbdf17331fea469e38c
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83e6edd6358326c9c2de31a54bb4a1ec50703f1f
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78279d2d74c58a0ed64e43cf601a02649771182e
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50bad78f03a02d3c0f228edf9912b494d3e7acb9
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/328c551f0cc81ee776b186b86cc6e5253bb6fda7
Web page

nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b9d605c3f0d3262142f196249cd3bd58c857c71

Vendor Advisories for CVE-2026-43449(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1112.119~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.253 (fixes >=5.10.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (123 versions)
  • every version up to 6.19.10-1: fixed in 6.19.10-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 240 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-18 03:40 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-17 14:13 UTCEG score recompute
  6. 2026-10-17 14:12 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  7. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-12 16:06 UTCEG score recompute
  12. 2026-10-11 19:48 UTCEG score recompute
  13. 2026-10-11 17:02 UTCEG score recompute
  14. 2026-10-11 14:28 UTCEG score recompute
  15. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 75 more
  1. 2026-09-30 07:58 UTCOSV refresh
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-09-11 14:23 UTCOSV refresh
  12. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-08-23 19:03 UTCEG score recompute
  26. 2026-08-23 19:03 UTCVendor advisory
  27. 2026-08-23 19:03 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  28. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-08-17 11:31 UTCEG score recompute
  35. 2026-08-17 11:31 UTCVendor advisory
  36. 2026-08-17 11:31 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  37. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-16 04:34 UTCEG score recompute
  39. 2026-08-16 04:34 UTCVendor advisory
  40. 2026-08-16 04:34 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  41. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-08-14 15:38 UTCVendor advisory
  44. 2026-08-14 15:38 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  45. 2026-08-14 03:08 UTCEG score recompute
  46. 2026-08-14 03:08 UTCVendor advisory
  47. 2026-08-14 03:08 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  48. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-08-13 05:59 UTCVendor advisory
  50. 2026-08-13 05:59 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  51. 2026-08-12 16:44 UTCEG score recompute
  52. 2026-08-12 16:44 UTCVendor advisory
  53. 2026-08-12 16:44 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  54. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-08-11 15:51 UTCEG score recompute
  56. 2026-08-11 15:51 UTCVendor advisory
  57. 2026-08-11 15:51 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  58. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-08-11 01:17 UTCEG score recompute
  60. 2026-08-11 01:17 UTCVendor advisory
  61. 2026-08-11 01:17 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  62. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  63. 2026-08-10 03:23 UTCVendor advisory
  64. 2026-08-10 03:23 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  65. 2026-08-09 14:53 UTCVendor advisory
  66. 2026-08-09 14:53 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  67. 2026-08-09 02:23 UTCEG score recompute
  68. 2026-08-09 02:23 UTCVendor advisory
  69. 2026-08-09 02:23 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  70. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  71. 2026-08-08 02:42 UTCEG score recompute
  72. 2026-08-08 02:42 UTCVendor advisory
  73. 2026-08-08 02:42 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1
  74. 2026-08-07 14:12 UTCVendor advisory
  75. 2026-08-07 14:12 UTCGHSA enrichmentGHSA-hv7m-w2x8-mf6q · GitHub severity HIGH · GitHub CVSS 7.1

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43449?
CVE-2026-43449 is a high-severity vulnerability; its CVE record was published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-pci: Fix slab-out-of-bounds in nvmedbbufset dev->onlinequeues is a count incremented in nvmeinit_queue. Thus, valid indices are 0 through dev->online_queues − 1. This patch fixes the loop condition to ensure the index stays…
When was the CVE record for CVE-2026-43449 published?
The CVE record for CVE-2026-43449 was published on May 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 21, 2026; the record at its source may have been updated since.
Is CVE-2026-43449 actively exploited?
CVE-2026-43449 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43449?
CVE-2026-43449 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-43449?
A fix for CVE-2026-43449 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43449 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43449

Explore →

Is Your Infrastructure Affected by CVE-2026-43449?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs