CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush()
Published Jul 9, 2025
·Updated
bcache: fix NULL pointer in cachesetflush()
Affected Software
11 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=3.10<5.10.240
Linux Linux kernel>=5.11<5.15.187
Linux Linux kernel>=5.16<6.1.143
Linux Linux kernel>=6.2<6.6.96
Linux Linux kernel>=6.7<6.12.36
Linux Linux kernel>=6.13<6.15.5
Debian Debian Linux=11.0
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.92.2-2
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Jul 9, 2025
CVE Published
via MITRE·10:42 AM
Data Sourced
via MITRE·10:42 AM
Description
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·12:00 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-38263?
CVE-2025-38263 has a medium severity level due to the potential for NULL pointer dereference which could lead to a denial of service.
2
How do I fix CVE-2025-38263?
To fix CVE-2025-38263, ensure you update to the latest version of the Linux kernel where this vulnerability has been patched.
3
Which versions of the Linux kernel are affected by CVE-2025-38263?
CVE-2025-38263 affects multiple versions of the Linux kernel prior to the patch inclusion.
4
What types of systems are at risk from CVE-2025-38263?
Systems running vulnerable versions of the Linux kernel are at risk from CVE-2025-38263.
5
Is CVE-2025-38263 exploitable remotely?
CVE-2025-38263 may be exploited by local attackers, but it is not designated as a remotely exploitable vulnerability.