CVE-2025-22036

Source
https://nvd.nist.gov/vuln/detail/CVE-2025-22036
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-22036.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-22036
Downstream
Related
Published
2025-04-16T15:15:56Z
Modified
2025-05-05T17:00:19Z
Severity
  • 7.0 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

exfat: fix random stack corruption after get_block

When getblock is called with a bufferhead allocated on the stack, such as dompagereadpage, stack corruption due to buffer_head UAF may occur in the following race condition situation.

 <CPU 0>                      <CPU 1>

mpagereadfolio <<bh on stack>> dompagereadpage exfatgetblock bhread _bhread getbh(bh) submitbh waitonbuffer ... endbufferreadsync _endbufferreadnotouch unlockbuffer <<keep going>> ... ... ... ... <<bh is not valid out of mpagereadfolio>> . . anotherfunction <<variable A on stack>> putbh(bh) atomicdec(bh->b_count) * stack corruption here *

This patch returns -EAGAIN if a folio does not have buffers when bhread needs to be called. By doing this, the caller can fallback to functions like blockreadfullfolio(), create a bufferhead in the folio, and then call getblock again.

Let's do not call bhread() with on-stack bufferhead.

References

Affected packages

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.12.25-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}