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-50218ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow Syzbot reported a kernel BUG in ocfs2_truncate_inline. There are two reasons for this: first, the parameter value passed is greater than ocfs2_max_inline_data_with_xattr, second, the start and end parameters of ocfs2_truncate_inline are "unsigned int". So, we need to add a sanity check for byte_start and byte_len right before ocfs2_truncate_inline() in ocfs2_remove_inode_range(), if they are greater than ocfs2_max_inline_data_with_xattr return -EINVAL.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 18 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-50218, 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.27% · top 80% of all CVEs (17 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 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < 27d95867bee806cdc448d122bd99f1d8b0544035
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < 95fbed8ae8c32c0977e6be1721c190d8fea23f2f
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < 70767689ec6ee5f05fb0a2c17d7ec1927946e486
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < ecd62f684386fa64f9c0cea92eea361f4e6444c2
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < 2fe5d62e122b040ce7fc4d31aa7fa96ae328cefc
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < 88f97a4b5843ce21c1286e082c02a5fb4d8eb473
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < 0b6b8c2055784261de3fb641c5d0d63964318e8f
    • affected 1afc32b952335f665327a1a9001ba1b44bb76fd9 – < bc0a2f3a73fcdac651fca64df39306d1e5ebe3b0
  • Linux · Linux

    • affected 2.6.24
    • unaffected < 2.6.24
    • unaffected 4.19.323 – ≤ 4.19.*
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.229 – ≤ 5.10.*
    • unaffected 5.15.171 – ≤ 5.15.*
    • unaffected 6.1.116 – ≤ 6.1.*
    • unaffected 6.6.60 – ≤ 6.6.*
    • unaffected 6.11.7 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .