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-58085tomoyo: don't emit warning in tomoyo_write_control()

Description

In the Linux kernel, the following vulnerability has been resolved: tomoyo: don't emit warning in tomoyo_write_control() syzbot is reporting too large allocation warning at tomoyo_write_control(), for one can write a very very long line without new line character. To fix this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE, for practically a valid line should be always shorter than 32KB where the "too small to fail" memory-allocation rule applies. One might try to write a valid line that is longer than 32KB, but such request will likely fail with -ENOMEM. Therefore, I feel that separately returning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant. There is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 20 months 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-58085, 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.21% · top 88% of all CVEs (16 Nov 2026)
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 bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < c67efabddc73171c7771d3ffe4ffa1e503ee533e
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < f6b37b3e12de638753bce79a2858070b9c4a4ad3
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < fe1c021eb03dae0dc9dce55e81f77a60e419a27a
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < c9382f380e8d09209b8e5c0def0545852168be25
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < 414705c0303350d139b1dc18f329fe47dfb642dd
    • affected bd03a3e4c9a9df0c6b007045fa7fc8889111a478 – < 3df7546fc03b8f004eee0b9e3256369f7d096685
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 5.4.291 – ≤ 5.4.*
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.78 – ≤ 6.6.*
    • unaffected 6.12.14 – ≤ 6.12.*
    • unaffected 6.13.3 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .