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… (CVE-2026-74610)
A vulnerability in the Linux kernel's TLS implementation was resolved where the plaintext sk_msg ring buffer could become full and unpushed, leading to a NULL pointer dereference. This occurs because the full_record flag was not set when the ring became full, causing subsequent operations to overwrite live entries and corrupt internal state. An unprivileged user can trigger this on a loopback TCP socket with the TLS ULP attached, potentially causing a kernel crash.
AI Analysis
Technical Summary
The Linux kernel TLS subsystem had a flaw in tls_sw_sendmsg_locked() where the plaintext sk_msg ring buffer could become full without setting the full_record flag. This caused the ring buffer pointers to wrap incorrectly, leading to overwriting of live fragments and a mismatch in scatterlist size. When the record was pushed, this caused the scatterwalk to read beyond bounds, resulting in a kernel NULL pointer dereference. The issue can be triggered by an unprivileged user on a loopback TCP socket with the TLS ULP attached. The fix involves setting the full_record flag when the ring becomes full and pushing a full record on entry to the sendmsg loop.
Potential Impact
An unprivileged local user can cause a kernel NULL pointer dereference, leading to a denial of service (kernel crash) on systems with the affected Linux kernel TLS implementation. There is no indication of privilege escalation or code execution from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to set the full_record flag correctly and push full records promptly, preventing the ring buffer corruption and subsequent crash. Users should apply the official Linux kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisory for current remediation guidance.
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… (CVE-2026-74610)
Description
A vulnerability in the Linux kernel's TLS implementation was resolved where the plaintext sk_msg ring buffer could become full and unpushed, leading to a NULL pointer dereference. This occurs because the full_record flag was not set when the ring became full, causing subsequent operations to overwrite live entries and corrupt internal state. An unprivileged user can trigger this on a loopback TCP socket with the TLS ULP attached, potentially causing a kernel crash.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel TLS subsystem had a flaw in tls_sw_sendmsg_locked() where the plaintext sk_msg ring buffer could become full without setting the full_record flag. This caused the ring buffer pointers to wrap incorrectly, leading to overwriting of live fragments and a mismatch in scatterlist size. When the record was pushed, this caused the scatterwalk to read beyond bounds, resulting in a kernel NULL pointer dereference. The issue can be triggered by an unprivileged user on a loopback TCP socket with the TLS ULP attached. The fix involves setting the full_record flag when the ring becomes full and pushing a full record on entry to the sendmsg loop.
Potential Impact
An unprivileged local user can cause a kernel NULL pointer dereference, leading to a denial of service (kernel crash) on systems with the affected Linux kernel TLS implementation. There is no indication of privilege escalation or code execution from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to set the full_record flag correctly and push full records promptly, preventing the ring buffer corruption and subsequent crash. Users should apply the official Linux kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mfgw-4w39-hh3m
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74610"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f3acd9273b499bc876
Added to database: 08/22/2026, 22:51:31 UTC
Last enriched: 08/22/2026, 23:26:14 UTC
Last updated: 08/23/2026, 01:00:22 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.