CVE-2026-80946

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

fuse: copy request headers via a stack buffer for io-uring

The fuse-io-uring transport copies req->in.h out to the ring in fuse_uring_copy_to_ring() and req->out.h back in fuse_uring_commit(). Both headers live inside the fuse_request slab object, whose cache (fuse_req_cachep) is created without a usercopy whitelist, so copying them directly to/from userspace trips CONFIG_HARDENED_USERCOPY and panics:

usercopy: Kernel memory exposure attempt detected from SLUB object 'fuse_request' (offset 56, size 40)! kernel BUG at mm/usercopy.c:102! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:usercopy_abort (mm/usercopy.c:90) Call Trace: __check_heap_object (mm/slub.c:8268) __check_object_size (mm/usercopy.c:197 mm/usercopy.c:258 mm/usercopy.c:223) copy_header_to_ring (fs/fuse/dev_uring.c:618) fuse_uring_prepare_send (fs/fuse/dev_uring.c:776 fs/fuse/dev_uring.c:785) fuse_uring_send_in_task (fs/fuse/dev_uring.c:1306) tctx_task_work_run (io_uring/tw.c:96) task_work_run (kernel/task_work.c:233) io_run_task_work (io_uring/tw.h:84) io_cqring_wait (io_uring/wait.c:278) __do_sys_io_uring_enter (io_uring/io_uring.c:2685) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)

Bounce both headers through an on-stack copy so the usercopy touches stack memory, not the slab object.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

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

September 11, 2026

Last Modified

September 11, 2026

References (3)

Vendor Advisories for CVE-2026-80946(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 13× in last 7d / 44× 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.

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. 1 repeat row among the latest 48 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 22:46 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  5. 2026-10-11 19:21 UTCEG score recompute
  6. 2026-10-11 16:37 UTCEG score recompute
  7. 2026-10-11 13:55 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-08 23:29 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-05 16:22 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-02 16:25 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  21. 2026-10-02 16:24 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-29 17:06 UTCEG score recompute
  25. 2026-09-29 17:06 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
Show 22 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-09-26 17:30 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-09-23 18:13 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-09-20 18:57 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  13. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-17 19:41 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-14 20:02 UTCEG score recompute
  19. 2026-09-14 20:02 UTCGHSA enrichmentGHSA-4p4j-8fxf-mvhp
  20. 2026-09-11 20:36 UTCNVD update
  21. 2026-09-11 19:55 UTCEG score recompute
  22. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80946?
CVE-2026-80946 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse: copy request headers via a stack buffer for io-uring The fuse-io-uring transport copies req->in.h out to the ring in fuseuringcopytoring() and req->out.h back in fuseuringcommit(). Both headers live inside the fuse_request…
When was the CVE record for CVE-2026-80946 published?
The CVE record for CVE-2026-80946 was published on September 11, 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 September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-80946 actively exploited?
CVE-2026-80946 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).
How do I remediate CVE-2026-80946?
A fix for CVE-2026-80946 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80946 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-80946

Explore →

Is Your Infrastructure Affected by CVE-2026-80946?

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

Book a Demo →Browse All CVEs