7.8

CVE-2024-38605: linux NULL Pointer Dereference

CVSS: 7.8v3.1HighModified
AliasesUBUNTU-CVE-2024-38605DEBIAN-CVE-2024-38605
Published 19-06-2024Last modified 05-08-2026

Vulnerability summary

CVE-2024-38605 is a high (CVSS 7.8) NULL Pointer Dereference vulnerability in linux. EPSS estimates a 0.75% chance of exploitation in the next 30 days, higher than 54% of scored vulnerabilities.

Overall risk
31/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.75%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 23 · Related 19

Timeline

  1. 19-06-2024
    PublishedVulnerability first disclosed.
  2. 05-08-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.75%

Chance of exploitation in the next 30 days

Percentile

54%

Versus all other CVEs

30-day change

0.00 pp

From 0.75% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.75%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu116 products
  • linux< 5.15.0-121.131 | < 6.8.0-40.40
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 5.15.0-1069.75 | < 6.8.0-1013.14
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < d7ff29a429b56f04783152ad7bbd7233b740e434 | ≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < e7e0ca200772bdb2fdc6d43d32d341e87a36f811 | ≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < e007476725730c1a68387b54b7629486d8a8301e | ≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92 | ≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < c935e72139e6d523defd60fe875c01eb1f9ea5c5 | ≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < 6b8374ee2cabcf034faa34e69a855dc496a9ec12 | ≥ 81033c6b584b44514cbb16fffc26ca29a0fa6270, < 39381fe7394e5eafac76e7e9367e7351138a29c1 | 5.9
  • linux_kernel≥ 5.9, < 5.10.219 | ≥ 5.11, < 5.15.161 | ≥ 5.16, < 6.1.93 | ≥ 6.2, < 6.6.33 | ≥ 6.7, < 6.8.12 | ≥ 6.9, < 6.9.3
Debian1 product
  • linux< 6.1.94-1 | < 6.8.12-1

3 vendors · 119 products

References

22 links
Show all 22 references