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-38619usb-storage: alauda: Check whether the media is initialized

Description

In the Linux kernel, the following vulnerability has been resolved: usb-storage: alauda: Check whether the media is initialized The member "uzonesize" of struct alauda_info will remain 0 if alauda_init_media() fails, potentially causing divide errors in alauda_read_data() and alauda_write_lba(). - Add a member "media_initialized" to struct alauda_info. - Change a condition in alauda_check_media() to ensure the first initialization. - Add an error check for the return value of alauda_init_media().

Timeline

  1. ID reserved

    By Linux

  2. · 2 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-38619, 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.25% · top 83% 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 e80b0fade09ef1ee67b0898d480d4c588f124d5f – < e0aab7b07a9375337847c9d74a5ec044071e01c8
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < 51fe16c058acb22f847e69bc598066ed0bcd5c15
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < f68820f1256b21466ff094dd97f243b7e708f9c1
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < 3eee13ab67f65606faa66e0c3c729e4f514838fd
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < e0e2eec76920a133dd49a4fbe4656d83596a1361
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < 2cc32639ec347e3365075b130f9953ef16cb13f1
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < 24bff7f714bdff97c2a75a0ff6a368cdf8ad5af4
    • affected e80b0fade09ef1ee67b0898d480d4c588f124d5f – < 16637fea001ab3c8df528a8995b3211906165a30
  • Linux · Linux

    • affected 2.6.16
    • unaffected < 2.6.16
    • unaffected 4.19.317 – ≤ 4.19.*
    • unaffected 5.4.279 – ≤ 5.4.*
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.95 – ≤ 6.1.*
    • unaffected 6.6.35 – ≤ 6.6.*
    • unaffected 6.9.6 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References12

Sources

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

Badge for a README or a ticket

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

Record last updated .