CVE-2026-43448

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-28754 (ENISA EUVD) · GHSA-938f-6jj9-x227 (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

nvme-pci: Fix race bug in nvme_poll_irqdisable()

In the following scenario, pdev can be disabled between (1) and (3) by (2). This sets pdev->msix_enabled = 0. Then, pci_irq_vector() will return MSI-X IRQ(>15) for (1) whereas return INTx IRQ(<=15) for (2). This causes IRQ warning because it tries to enable INTx IRQ that has never been disabled before.

To fix this, save IRQ number into a local variable and ensure disable_irq() and enable_irq() operate on the same IRQ number. Even if pci_free_irq_vectors() frees the IRQ concurrently, disable_irq() and enable_irq() on a stale IRQ number is still valid and safe, and the depth accounting reamins balanced.

task 1: nvme_poll_irqdisable() disable_irq(pci_irq_vector(pdev, nvmeq->cq_vector)) ...(1) enable_irq(pci_irq_vector(pdev, nvmeq->cq_vector)) ...(3)

task 2: nvme_reset_work() nvme_dev_disable() pdev->msix_enable = 0; ...(2)

crash log:

------------[ cut here ]------------ Unbalanced enable for IRQ 10 WARNING: kernel/irq/manage.c:753 at __enable_irq+0x102/0x190 kernel/irq/manage.c:753, CPU#1: kworker/1:0H/26 Modules linked in: CPU: 1 UID: 0 PID: 26 Comm: kworker/1:0H Not tainted 6.19.0-dirty #9 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: kblockd blk_mq_timeout_work RIP: 0010:__enable_irq+0x107/0x190 kernel/irq/manage.c:753 Code: ff df 48 89 fa 48 c1 ea 03 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 04 84 d2 75 79 48 8d 3d 2e 7a 3f 05 41 8b 74 24 2c <67> 48 0f b9 3a e8 ef b9 21 00 5b 41 5c 5d e9 46 54 66 03 e8 e1 b9 RSP: 0018:ffffc900001bf550 EFLAGS: 00010046 RAX: 0000000000000007 RBX: 0000000000000000 RCX: ffffffffb20c0e90 RDX: 0000000000000000 RSI: 000000000000000a RDI: ffffffffb74b88f0 RBP: ffffc900001bf560 R08: ffff88800197cf00 R09: 0000000000000001 R10: 0000000000000003 R11: 0000000000000003 R12: ffff8880012a6000 R13: 1ffff92000037eae R14: 000000000000000a R15: 0000000000000293 FS: 0000000000000000(0000) GS:ffff8880b49f7000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000555da4a25fa8 CR3: 00000000208e8000 CR4: 00000000000006f0 Call Trace: enable_irq+0x121/0x1e0 kernel/irq/manage.c:797 nvme_poll_irqdisable+0x162/0x1c0 drivers/nvme/host/pci.c:1494 nvme_timeout+0x965/0x14b0 drivers/nvme/host/pci.c:1744 blk_mq_rq_timed_out block/blk-mq.c:1653 [inline] blk_mq_handle_expired+0x227/0x2d0 block/blk-mq.c:1721 bt_iter+0x2fc/0x3a0 block/blk-mq-tag.c:292 __sbitmap_for_each_set include/linux/sbitmap.h:269 [inline] sbitmap_for_each_set include/linux/sbitmap.h:290 [inline] bt_for_each block/blk-mq-tag.c:324 [inline] blk_mq_queue_tag_busy_iter+0x969/0x1e80 block/blk-mq-tag.c:536 blk_mq_timeout_work+0x627/0x870 block/blk-mq.c:1763 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 irq event stamp: 74478 hardirqs last enabled at (74477): [] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline] hardirqs last enabled at (74477): [] _raw_spin_unlock_irq+0x2c/0x60 kernel/locking/spinlock.c:202 hardirqs last disabled at (74478): [] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline] hardirqs last disabled at (74478): [] _raw_spin_lock_irqsave+0x85/0xa0 kernel/locking/spinlock.c:162 softirqs last enabled at (74304): [] __do_softirq kernel/softirq.c:656 [inline] softirqs last enabled at (74304): [] invoke_softirq kernel/softirq.c:496 [inline] softirqs last enabled at (74304): [] __irq_exit_rcu+0xdc/0x120 ---truncated---

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation<0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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.1%
EPSS %ILE
below the 1st
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

November 11, 2026

Advisory Details (6)

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

nvme-pci: Fix race bug in nvme_poll_irqdisable() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-pci: Fix race bug in nvme_poll_irqdisable() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-pci: Fix race bug in nvme_poll_irqdisable() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-pci: Fix race bug in nvme_poll_irqdisable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/843e913cef4e33723663a899727f685a95ab53fe
Web page

nvme-pci: Fix race bug in nvme_poll_irqdisable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/628773eba024d1107cc9ec157a682cbb42ac912a
Web page

nvme-pci: Fix race bug in nvme_poll_irqdisable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/265dbc9bc33c29f60f90be3e0afe1c4067ebb70b

Vendor Advisories for CVE-2026-43448(1)

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
linuxKernel @ 6.1.167 (fixes >=5.7.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 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
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 (126 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

(14)

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 6× in last 7d / 25× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 230 rows 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 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43448?
CVE-2026-43448 is a medium-severity vulnerability; its CVE record was published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-pci: Fix race bug in nvme_poll_irqdisable() In the following scenario, pdev can be disabled between (1) and (3) by (2). This sets pdev->msix_enabled = 0. Then, pci_irq_vector() will return MSI-X IRQ(>15) for (1) whereas return…
When was the CVE record for CVE-2026-43448 published?
The CVE record for CVE-2026-43448 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 November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-43448 actively exploited?
CVE-2026-43448 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43448?
CVE-2026-43448 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-43448?
A fix for CVE-2026-43448 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43448 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-43448

Explore →

Is Your Infrastructure Affected by CVE-2026-43448?

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

Book a Demo →Browse All CVEs