Local service interruption via uninitialized sysctl ownership
Published Aug 17, 2024 · Updated May 23, 2026
Improper initialization in Linux kernel 5.3 and affected stable branches allows local users to interrupt service through /proc/sys inode handling. The sysctl inode path leaves i_uid and i_gid without safe defaults, and net_ctl_set_ownership can return without replacing them when owner calculation fails. Low-privileged local access is required; published sources bound the effect to availability but do not identify the precise interruption mode.
Summary
What happened
Improper initialization in Linux kernel 5.3 and affected stable branches allows local users to interrupt service through /proc/sys inode handling. The sysctl inode path leaves i_uid and i_gid without safe defaults, and net_ctl_set_ownership can return without replacing them when owner calculation fails. Low-privileged local access is required; published sources bound the effect to availability but do not identify the precise interruption mode.
The record
- CVE
- CVE-2024-42312
- Published
- Aug 17, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-20, CWE-908, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record 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=0 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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