# filemap: Handle sibling entries in filemap_get_read_batch()

CVE record · `CVE-2022-49699`

- **Identifiers:** `CVE-2022-49699`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `cbd59c48ae2bcadc4a7599c29cf32fd3f9b78251 to before a66f131d30e53000f08301776bf85c912ef47aad` (git)
  - affected: `cbd59c48ae2bcadc4a7599c29cf32fd3f9b78251 to before cb995f4eeba9d268fd4b56c2423ad6c1d1ea1b82` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.12`
  - unaffected: `before 5.12` (semver)
  - unaffected: `5.18.8 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel is affected from version 5.12 until the fixes, which address a race in filemap_get_read_batch() where a read overlapping an invalidation can dereference a NULL pointer while holding the RCU read lock. The source does not say what access an attacker needs. Upgrade to a kernel that includes the fix, such as 5.18.8 or later in the 5.18 series, or 5.19 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 02:24 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49699)
- 26 Feb 2025, 07:01 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49699)

## Sources

- [CVE List: CVE-2022-49699](https://www.cve.org/CVERecord?id=CVE-2022-49699)
- [NVD: CVE-2022-49699](https://nvd.nist.gov/vuln/detail/CVE-2022-49699)

### References from the CNA

- <https://git.kernel.org/stable/c/a66f131d30e53000f08301776bf85c912ef47aad>
- <https://git.kernel.org/stable/c/cb995f4eeba9d268fd4b56c2423ad6c1d1ea1b82>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49699>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49699/>. Everything for agents: <https://agentprime.io/llms.txt>.
