CVE-2026-80852

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-71302 (ENISA EUVD) · GHSA-3586-6wjw-9g84 (GitHub Security Advisories)Source: ENISA EUVD

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

tls: device: fix out-of-bounds write in tls_append_frag()

Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.

tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check. The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS]. Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.

The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.

Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.

BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269) Write of size 8 at addr ffff8881104d1530 by task tls_oob/450

CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT Call Trace: dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) tls_append_frag (net/tls/tls_device.c:269) tls_push_data (net/tls/tls_device.c:518) tls_device_sendmsg (net/tls/tls_device.c:583) inet_sendmsg (net/ipv4/af_inet.c:865) sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813) splice_to_socket (fs/splice.c:884) do_splice (fs/splice.c:936 fs/splice.c:1349) __do_splice (fs/splice.c:1431) __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)

and, once the record is pushed:

UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24 index 18 is out of range for type 'skb_frag_t [17]' UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41 index 18 is out of range for type 'scatterlist [17]' UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39 index 18 is out of range for type 'scatterlist [17]' UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38 index 26 is out of range for type 'scatterlist [17]'

kernel tried to execute NX-protected page - exploit attempt? (uid: 0) BUG: unable to handle page fault for address: ffffea000411a680 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0011) - permissions violation Oops: Oops: 0011 [#1] SMP KASAN PTI Workqueue: ktls_device_destruct 0xffffea000411a680 RIP: 0010:0xffffea000411a680 Call Trace: worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

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

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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 BOD 26-04 block below.

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 4, 2026

Last Modified

October 19, 2026

Vendor Advisories for CVE-2026-80852(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (172 versions)
  • every version up to 7.1.13-1: fixed in 7.1.13-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 50× 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 82 is merged into the row it repeats.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-25 13:59 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-19 09:25 UTCNVD update
  11. 2026-10-19 09:23 UTCEG score recompute
  12. 2026-10-19 09:23 UTCVendor advisory
  13. 2026-10-19 09:23 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  14. 2026-10-19 08:58 UTCMITRE cvelistV5
  15. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-18 03:09 UTCEG score recompute
  17. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-12 14:57 UTCEG score recompute
  24. 2026-10-11 19:21 UTCEG score recompute
  25. 2026-10-11 16:37 UTCEG score recompute
Show 56 more
  1. 2026-10-11 13:55 UTCEG score recompute
  2. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-09 23:08 UTCVendor advisory
  5. 2026-10-09 23:08 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-06 13:38 UTCVendor advisory
  11. 2026-10-06 13:38 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-03 16:16 UTCVendor advisory
  15. 2026-10-03 16:16 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-09-30 18:54 UTCEG score recompute
  20. 2026-09-30 18:54 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  21. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-27 20:37 UTCVendor advisory
  24. 2026-09-27 20:37 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-24 23:15 UTCVendor advisory
  29. 2026-09-24 23:15 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  30. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-09-22 01:31 UTCVendor advisory
  34. 2026-09-22 01:31 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  35. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-09-19 04:10 UTCVendor advisory
  38. 2026-09-19 04:10 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  39. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-09-16 06:48 UTCVendor advisory
  42. 2026-09-16 06:48 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  43. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-09-13 09:26 UTCVendor advisory
  46. 2026-09-13 09:25 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  47. 2026-09-10 12:03 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  48. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-09-07 14:40 UTCEG score recompute
  50. 2026-09-07 14:40 UTCVendor advisory
  51. 2026-09-07 14:40 UTCGHSA enrichmentGHSA-3586-6wjw-9g84
  52. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-09-04 16:22 UTCNVD update
  55. 2026-09-04 16:05 UTCEG score recompute
  56. 2026-09-04 16:04 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80852?
CVE-2026-80852 is a vulnerability whose severity is not yet rated; its CVE record was published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: tls: device: fix out-of-bounds write in tlsappendfrag() Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that…
When was the CVE record for CVE-2026-80852 published?
The CVE record for CVE-2026-80852 was published on September 4, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-80852 actively exploited?
CVE-2026-80852 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-80852?
A fix for CVE-2026-80852 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80852 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-80852

Explore →

Is Your Infrastructure Affected by CVE-2026-80852?

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