CVE-2025-38648
What it is
In the Linux kernel, the following vulnerability has been resolved: spi: stm32: Check for cfg availability in stm32_spi_probe The stm32_spi_probe function now includes a check to ensure that the pointer returned by of_device_get_match_data is not NULL before accessing its members. This resolves a warning where a potential NULL pointer dereference could occur when accessing cfg->has_device_mode. Before accessing the 'has_device_mode' member, we verify that 'cfg' is not NULL. If 'cfg' is NULL, an error message is logged. This change ensures that the driver does not attempt to access configuration data if it is not available, thus preventing a potential system crash due to a NULL pointer dereference.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6.102
- Linux Kernel < 6.12.42
- Linux Kernel < 6.15.10
- Linux Kernel < 6.16.1
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38648.md and follow it. Check whether this project is affected by CVE-2025-38648. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/21f1c800f6620e43f31dfd76709dbac8ebaa5a16
- https://git.kernel.org/stable/c/3a571a8d52272cc26858ab1bc83d0f66e5dee938
- https://git.kernel.org/stable/c/6031a54f4eac921efe6122a561d44df89b37f2d4
- https://git.kernel.org/stable/c/a7645815edf4478f3258bb0db95a08986a77f5c0
- https://git.kernel.org/stable/c/cc063d23ad80ef7d201c41b2716b1bae7c662cf9
References
- https://git.kernel.org/stable/c/21f1c800f6620e43f31dfd76709dbac8ebaa5a16
- https://git.kernel.org/stable/c/3a571a8d52272cc26858ab1bc83d0f66e5dee938
- https://git.kernel.org/stable/c/6031a54f4eac921efe6122a561d44df89b37f2d4
- https://git.kernel.org/stable/c/a7645815edf4478f3258bb0db95a08986a77f5c0
- https://git.kernel.org/stable/c/cc063d23ad80ef7d201c41b2716b1bae7c662cf9