Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-42312, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf – < b2591c89a6e2858796111138c38fcb6851aa1955
    • affected 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf – < 34a86adea1f2b3c3f9d864c8cce09dca644601ab
    • affected 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf – < 1deae34db9f4f8e0e03f891be2e2e15c15c8ac05
    • affected 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf – < ffde3af4b29bf97d62d82e1d45275587e10a991a
    • affected 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf – < c7e2f43d182f5dde473389dbb39f16c9f0d64536
    • affected 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf – < 98ca62ba9e2be5863c7d069f84f7166b45a5b2f4
    • affected e83234d7ef237931148b4b17834dadf57eb46c12
    • affected 2cbf2af144f0cd08a3361c6299b2e6086b7d21d9
    • affected 2c7b50c7b1d036f71acd9a917a8cb0f9b6e43dab
    • affected 7eb45a94c279dd5af4cafaa738ae93737517eef4
    • affected 14cc90952cef94bfa89a6b4a2f55fd9a70f50a16
    • affected 4.9.187 – < 4.10
    • affected 4.14.135 – < 4.15
    • affected 4.19.61 – < 4.20
    • affected 5.1.20 – < 5.2
    • affected 5.2.3 – < 5.3
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.10.224 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.104 – ≤ 6.1.*
    • unaffected 6.6.45 – ≤ 6.6.*
    • unaffected 6.10.3 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-42312 badge
[![CVE-2024-42312](https://cveledger.app/badge/CVE-2024-42312.svg)](https://cveledger.app/cve/CVE-2024-42312)

Record last updated .