Kernel-state byte disclosure via empty-list confusion
Published Mar 27, 2023 · Updated Feb 24, 2025
Type confusion in the Linux Kernel net/tls stack allows local users to disclose one kernel-state byte through a TLS socket. The tls_is_tx_ready() path calls list_first_entry() on an empty tx_list, treats the list head as a TLS record, and reads the byte overlapping rec->tx_ready. Exploitation requires local low-privilege access and reaches only that byte; no integrity or availability impact is reported.
Summary
What happened
Type confusion in the Linux Kernel net/tls stack allows local users to disclose one kernel-state byte through a TLS socket. The tls_is_tx_ready() path calls list_first_entry() on an empty tx_list, treats the list head as a TLS record, and reads the byte overlapping rec->tx_ready. Exploitation requires local low-privilege access and reaches only that byte; no integrity or availability impact is reported.
The record
- CVE
- CVE-2023-1075
- Published
- Mar 27, 2023
- Updated
- Feb 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-843, CWE-200
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2023CVE publishedPublication date reported by the CVE source.
- Feb 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unknown
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo