CVE-2024-50198: Linux kernel · NULL Pointer Dereference
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 29 Oct 2026, 23:15 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
AI-suggested
A fix for this issue has been applied in the Linux kernel source to correctly use dev_to_iio_dev() for device retrieval. Users should update to the fixed kernel version containing this patch to resolve the segmentation fault.
Description
CVE-2024-50198 is a vulnerability in the Linux kernel's veml6030 light sensor driver. The issue arises from incorrect device pointer usage in the in_illuminance_period_available_show function, causing a NULL assignment and resulting in a segmentation fault when reading the attribute. This bug has existed since the driver's initial introduction and affects the stability of the kernel module.
References
- nvd.nist.gov/vuln/detail/CVE-2024-50198 (opens in a new tab)
- git.kernel.org/stable/c/2cbb41abae65626736b8b52cf3b9339612c5a86a (opens in a new tab)
- git.kernel.org/stable/c/50039aec43a82ad2495f2d0fb0c289c8717b4bb2 (opens in a new tab)
- git.kernel.org/stable/c/905166531831beb067fffe2bdfc98031ffe89087 (opens in a new tab)
- git.kernel.org/stable/c/bcb90518ccd9e10bf6ab29e31994aab93e4a4361 (opens in a new tab)
- git.kernel.org/stable/c/bf3ab8e1c28f10df0823d4ff312f83c952b06a15 (opens in a new tab)
- git.kernel.org/stable/c/c7c44e57750c31de43906d97813273fdffcf7d02 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html (opens in a new tab)