net: tls: prevent chain-after-chain in plain text SG
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.5, 5.10.258, 5.15.209, 6.1.175, 6.6.142, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in 49a5faaa471ddcd37b6893970c9916eb836e7c31; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in 91359966e247c0244c66d50bbb8e74aefa4321c3; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in 410351158dfef2d67fea6603680b3a6013c6ed9d; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in acdc12b71c9aa4be5dcd2c8062753c6d2033e235; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in 929b1548e63ac72e104c07d8ee8cbbeeba2fa89a; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in af855f4c966afafef74faf8390c7b86568c0d46d; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36; From 9aaaa56845a06aeabdd597cbe19492dc01f281ec · fixed in ff26a0e8377dec07e4a7230db7675bed1b9a6d03; From 5.4.14 · fixed in 5.5
- Linux Linux
5.5
- KernelLinux
From 5.5.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.142; From 6.7.0 · fixed in 6.12.92; From 6.13.0 · fixed in 6.18.34; From 6.19.0 · fixed in 7.0.11
References 8
git.kernel.org
- stable/c/49a5faaa471ddcd37b6893970c9916eb836e7c31
- stable/c/91359966e247c0244c66d50bbb8e74aefa4321c3
- stable/c/410351158dfef2d67fea6603680b3a6013c6ed9d
- stable/c/acdc12b71c9aa4be5dcd2c8062753c6d2033e235
- stable/c/929b1548e63ac72e104c07d8ee8cbbeeba2fa89a
- stable/c/af855f4c966afafef74faf8390c7b86568c0d46d
- stable/c/b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36
- stable/c/ff26a0e8377dec07e4a7230db7675bed1b9a6d03