tls: don't leave a full plaintext sk_msg ring unpushed
Summary
| CVE | CVE-2026-74610 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-08-22 16:16:33 UTC |
|---|
| Updated | 2026-08-22 16:16:33 UTC |
|---|
| Description | In the Linux kernel, the following vulnerability has been resolved:
tls: don't leave a full plaintext sk_msg ring unpushed
When the copy path in tls_sw_sendmsg_locked() adds the fragment that fills
the plaintext sk_msg ring, it does not set full_record, so the record is
left full and unpushed. A later splice() then adds to an already full
ring: sk_msg_page_add() has no fullness check of its own, so sg.end wraps
onto sg.start and the ring appears empty. Fragments added after that
overwrite live entries, and sg.size no longer matches what is reachable
between sg.start and sg.end, so pushing the record runs the scatterwalk off
the end of the scatterlist.
An unprivileged user can trigger this on a loopback TCP socket with the
"tls" ULP attached:
BUG: kernel NULL pointer dereference, address: 0000000000000008
RIP: 0010:memcpy_from_scatterwalk+0x32/0xc0
Call Trace:
skcipher_walk_next+0x1d1/0x2c0
gcm_encrypt_aesni_avx+0x1e9/0x220
bpf_exec_tx_verdict+0x3bb/0x860
tls_sw_sendmsg+0xa1a/0xca0
__sys_sendto+0x1da/0x1f0
Set full_record in the copy path when the ring becomes full, and push a
record that is already full on entry to the sendmsg loop. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected fe1e81d4f73b6cbaed4fcc476960d26770642842 aa8b14647721b5a4958712b35cf43e3125d47753 git |
Not specified |
| CNA |
Linux |
Linux |
affected fe1e81d4f73b6cbaed4fcc476960d26770642842 f634289a0b557a197c5f37284b623cefedfe73d5 git |
Not specified |
| CNA |
Linux |
Linux |
affected fe1e81d4f73b6cbaed4fcc476960d26770642842 3fc5044796dd87b8d68be4207046f5ce2748174c git |
Not specified |
| CNA |
Linux |
Linux |
affected fe1e81d4f73b6cbaed4fcc476960d26770642842 3c5f8f2aa57c647b83add4896aab64aac5fdedad git |
Not specified |
| CNA |
Linux |
Linux |
affected fe1e81d4f73b6cbaed4fcc476960d26770642842 7bca91d63341274e857f4aeaad54d229405e93dc git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.5 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.5 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.152 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.104 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.45 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.9 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/3c5f8f2aa57c647b83add4896aab64aac5fdedad |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f634289a0b557a197c5f37284b623cefedfe73d5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7bca91d63341274e857f4aeaad54d229405e93dc |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/aa8b14647721b5a4958712b35cf43e3125d47753 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3fc5044796dd87b8d68be4207046f5ce2748174c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.