CVE-20XX-?

CVE-2022-49699

5.5 MEDIUM 0.2% exploit odds Fix listed Memory safety OS & kernel

What it is

In the Linux kernel, the following vulnerability has been resolved: filemap: Handle sibling entries in filemap_get_read_batch() If a read races with an invalidation followed by another read, it is possible for a folio to be replaced with a higher-order folio. If that happens, we'll see a sibling entry for the new folio in the next iteration of the loop. This manifests as a NULL pointer dereference while holding the RCU read lock. Handle this by simply returning. The next call will find the new folio and handle it correctly. The other ways of handling this rare race are more complex and it's just not worth it.

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

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Details

Published
Last modified
Exploit probability
0.2% · EPSS, next 30 days
Weakness
CWE-476 · NULL pointer dereference
Record status
Analyzed

Affected

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

Meme: I wake up, CVE-2022-49699
Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record