CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 03ced5da6120965d80ed56dbb7d78fa5c9128906, 1fc6eb0c756b8be693b72e9e636ae5e236dcb6ee, 7e1208c135618358da5d7d6664874dc6e53c62fc; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 03ced5da6120965d80ed56dbb7d78fa5c9128906, 1fc6eb0c756b8be693b72e9e636ae5e236dcb6ee, 7e1208c135618358da5d7d6664874dc6e53c62fc; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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: <TASK> 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) </TASK> 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: <TASK> 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) </TASK>
- Published
- Sep 4, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.18affected
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before bc09411a11b5a676c59ff8612c6873d014f6fb36affected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before 1fc6eb0c756b8be693b72e9e636ae5e236dcb6eeaffected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before 03ced5da6120965d80ed56dbb7d78fa5c9128906affected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before a832d7cb09da2a8e4e9734b4be14d3e76169d805affected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before b7f10d4ff987bda038df90052cd4a1434a7412d4affected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before fadbc1ed2a872a8649a44cf9e1cf9621fc58cd6eaffected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before cd7e875b89597f3498917af764758391338d1802affected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before 7e1208c135618358da5d7d6664874dc6e53c62fcaffected · git
- e8f69799810c32dd40c6724d829eccc70baad07f and later · before b17cf742eaad70ae29ac558cefb3aa9bbeea03d4affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.13-1 | 7.1.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80850Sep 4, 2026 · tcp: fix AO info use-after-free in tcp_ao_connect_init()0Monitor
- ← EarlierCVE-2026-80851Sep 4, 2026 · gtp: serialize PDP context updates0Monitor
- Later →CVE-2026-80853Sep 4, 2026 · KVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 03ced5da6120965d80ed56dbb7d78fa5c9128906 | Vendor (CNA) |
| Linux Linux | 1fc6eb0c756b8be693b72e9e636ae5e236dcb6ee | Vendor (CNA) |
| Linux Linux | 7e1208c135618358da5d7d6664874dc6e53c62fc | Vendor (CNA) |
| Linux Linux | a832d7cb09da2a8e4e9734b4be14d3e76169d805 | Vendor (CNA) |
| Linux Linux | b17cf742eaad70ae29ac558cefb3aa9bbeea03d4 | Vendor (CNA) |
| Linux Linux | b7f10d4ff987bda038df90052cd4a1434a7412d4 | Vendor (CNA) |
| Linux Linux | bc09411a11b5a676c59ff8612c6873d014f6fb36 | Vendor (CNA) |
| Linux Linux | cd7e875b89597f3498917af764758391338d1802 | Vendor (CNA) |
| Linux Linux | fadbc1ed2a872a8649a44cf9e1cf9621fc58cd6e | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/1fc6eb0c756b8be693b72e9e636ae5e236dcb6ee
- git.kernel.org/stable/c/7e1208c135618358da5d7d6664874dc6e53c62fc
- git.kernel.org/stable/c/a832d7cb09da2a8e4e9734b4be14d3e76169d805
- git.kernel.org/stable/c/b17cf742eaad70ae29ac558cefb3aa9bbeea03d4
- git.kernel.org/stable/c/b7f10d4ff987bda038df90052cd4a1434a7412d4
- git.kernel.org/stable/c/bc09411a11b5a676c59ff8612c6873d014f6fb36
- git.kernel.org/stable/c/cd7e875b89597f3498917af764758391338d1802
- git.kernel.org/stable/c/fadbc1ed2a872a8649a44cf9e1cf9621fc58cd6e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.