# jbd2: fix deadlock in jbd2_journal_cancel_revoke()

CVE record · `CVE-2026-46061`

- **Identifiers:** `CVE-2026-46061`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 May 2026
- **Updated:** 14 Jun 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 May 2026, 12:57 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: `f1c5aa614b5c251f93a6a4c8c26001d5e9e53fd6 to before dff07cc98fdf6af57a7c054dc09b2050a9d5c287` (git)
  - affected: `f76d4c28a46a9260d85e00dafc8f46d369365d33 to before 2b2fee890250ab647a601124471a334bb01a0790` (git)
  - affected: `f76d4c28a46a9260d85e00dafc8f46d369365d33 to before bbd943d6a2d566428324b516a37f98328dfb802d` (git)
  - affected: `f76d4c28a46a9260d85e00dafc8f46d369365d33 to before 981fcc5674e67158d24d23e841523eccba19d0e7` (git)
  - affected: `1bb7a4b6b3d7dd8da6f5a9d0529d42c22a359e71` (git)
  - affected: `6.12.31 to before 6.12.86` (semver)
  - affected: `6.14.9 to before 6.15` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.15`
  - unaffected: `before 6.15` (semver)
  - unaffected: `6.12.86 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.27 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.4 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## 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.0009, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 27 May 2026. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/dff07cc98fdf6af57a7c054dc09b2050a9d5c287>
- <https://git.kernel.org/stable/c/2b2fee890250ab647a601124471a334bb01a0790>
- <https://git.kernel.org/stable/c/bbd943d6a2d566428324b516a37f98328dfb802d>
- <https://git.kernel.org/stable/c/981fcc5674e67158d24d23e841523eccba19d0e7>

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-2026-46061>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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