LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42312: sysctl: always initialize i_uid/i_gid

In the Linux kernel, the following vulnerability has been resolved: sysctl: always initialize i_uid/i_gid Always initialize i_uid/i_gid inside the sysfs core so set_ownership() can safely skip setting them. Commit 5ec27ec735ba ("fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.") added defaults for i_uid/i_gid when set_ownership() was not implemented. It also missed adjusting net_ctl_set_ownership() to use the same default values in case the computation of a better value failed.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue concerns incorrect initialization of ownership fields for sysctl-related inodes. The public record does not provide a CVSS score, CWE, impact statement, or exploitation evidence, so business urgency should be driven by kernel exposure and vendor advisories rather than assumed severity.

Executive priority

Track this as a kernel hygiene and vendor patch-management item, not a confirmed emergency. Prioritize systems where Linux kernel updates are delayed, vendor firmware is slow-moving, or operational exposure is high.

Technical view

The resolved defect initializes i_uid and i_gid consistently so set_ownership() can safely skip setting them. The bug came from earlier defaults for /proc/sys inode ownership that did not cover net_ctl_set_ownership() failure paths. Kernel stable commits and downstream Debian and Siemens advisories are referenced.

Likely exposure

Linux systems running affected kernel versions or vendor builds that include the vulnerable sysctl ownership handling may be exposed. Debian LTS and Siemens advisories indicate downstream relevance. Confirm exposure by checking the exact kernel package, vendor advisory status, and whether the stable fixes are present.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not describe exploit prerequisites, practical impact, or public weaponization. Treat exploitation status as unproven from these sources.

Researcher notes

Public details are limited to the kernel fix rationale and downstream advisories. The record does not supply CVSS, CWE, affected CPEs, or exploitability details. Avoid inferring privilege escalation, information disclosure, or denial-of-service without additional vendor evidence.

Mitigation direction

  • Apply kernel updates from the relevant Linux distribution or device vendor.
  • Check Debian LTS advisories if using Debian-derived long-term support kernels.
  • Check Siemens SSA-265688 for affected Siemens products and vendor guidance.
  • If no vendor package is available, verify whether the referenced stable commits are backported.

Validation and detection

  • Inventory running kernel versions across servers, appliances, containers hosts, and embedded devices.
  • Compare installed kernel packages against vendor advisories and fixed stable commits.
  • Confirm the deployed kernel changelog includes the sysctl i_uid/i_gid initialization fix.
  • Prioritize validation on internet-facing, multi-user, or vendor-managed Linux systems.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42312 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5ec27ec735ba0477d48c80561cc5e856f0c5dfaf, 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf, 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf, 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf, 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf, 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf, e83234d7ef237931148b4b17834dadf57eb46c12, 2cbf2af144f0cd08a3361c6299b2e6086b7d21d9, 2c7b50c7b1d036f71acd9a917a8cb0f9b6e43dab, 7eb45a94c279dd5af4cafaa738ae93737517eef4, 14cc90952cef94bfa89a6b4a2f55fd9a70f50a16, 4.9.187, 4.14.135, 4.19.61, 5.1.20, 5.2.3unaffected
LinuxLinux5.3, 0, 5.10.224, 5.15.165, 6.1.104, 6.6.45, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.