CVE-2026-46253 - In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persist

CVE-2026-46253 + In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persist + High + 2026-06-03

One-sentence business risk

A small malicious input can exhaust workers or crash services, creating a customer-visible availability incident.

Research notes

  • Root cause: In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persistent_ram_save_old() persistent_ram_save_old() can be called multiple times for the same persistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_g.
  • Affected versions: Affected versions named by the upstream advisory and dependency metadata.
  • Fixed / safe versions: Apply the Ubuntu package versions named in the linked USN notice or the upstream fixed release.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Exact vulnerable code pattern

memcpy(dst, src, user_len); parse_nested(untrusted, no_depth_limit);

Fixed / mitigated code pattern

bounds-check length before copy, cap parser depth/counts, and reject malformed frames before allocation

Dependency or runtime update:

rg -n "affected component|CVE-2026-46253" .
# update affected runtime/product to Apply the Ubuntu package versions named in the linked USN notice or the upstream fixed release

Step-by-step integration guide

  1. Inventory affected component across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to Apply the Ubuntu package versions named in the linked USN notice or the upstream fixed release or apply the exact vendor patch referenced below.
  3. Replace the vulnerable memory-corruption pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-46253-in-the-linux-kernel-the-following-vulnerability-
source: "Ubuntu Security Notices + NVD bulk"
dependency_or_product: "affected component"
affected: "Affected versions named by the upstream advisory and dependency metadata"
fixed: "Apply the Ubuntu package versions named in the linked USN notice or the upstream fixed release"
signals:
  - "memory-corruption"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-46253 (In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persist) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Apply the Ubuntu package versions named in the linked USN notice or the upstream fixed release. Replace the vulnerable memory-corruption pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-46253, memory-corruption, affected component, Ubuntu Security Notices + NVD bulk.
  • Affected tech stack: general.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References