CVE-2026-64046Critical· 9.8▾ MidnightIn the Linux kernel, the following vulnerability has been resolved: net: tls: prevent chain-after-chain in plain text SG Sashiko points out that if end = 0 (start != 0) the current code will create a chain link to content type right af…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.5%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
net: tls: prevent chain-after-chain in plain text SG
Sashiko points out that if end = 0 (start != 0) the current code will create a chain link to content type right after the wrap link:
This would create a chain where the wrap link points directly to another chain link. The scatterlist API sg_next iterator does not recursively resolve consecutive chain links.
meaning this is illegal input to crypto.
The wrapping link is unnecessary if end = 0. end is the entry after the last one used so end = 0 means there's nothing pushed after the wrap:
end start i v v v [ ]...[ ][ d ][ d ][ d ][ d ][rsv for wrap]
Skip the wrapping in this case.
TLS 1.3 can use the "wrapping slot" for it's chaining if end = 0. This avoids the chain-after-chain.
Move the wrap chaining before marking END and chaining off content type, that feels like more logical ordering to me, but should not matter from functional perspective.
Linux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < 49a5faaa471ddcd37b6893970c9916eb836e7c31Linux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < 91359966e247c0244c66d50bbb8e74aefa4321c3Linux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < 410351158dfef2d67fea6603680b3a6013c6ed9dLinux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < acdc12b71c9aa4be5dcd2c8062753c6d2033e235Linux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < 929b1548e63ac72e104c07d8ee8cbbeeba2fa89aLinux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < af855f4c966afafef74faf8390c7b86568c0d46dLinux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36Linux >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec < ff26a0e8377dec07e4a7230db7675bed1b9a6d03Linux d529d6c9f7e3aaeac13c4948f79799ccb825f29dLinux >= 5.4.14 < 5.5Linux 5.5Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets