{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2025-39789",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2025-39789"
  ],
  "published": "2025-09-11T16:57:02Z",
  "summary": "crypto: x86/aegis - Add missing error checks",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: x86/aegis - Add missing error checks\n\nThe skcipher_walk functions can allocate memory and can fail, so\nchecking for errors is necessary.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-39789"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/475104178f4d30e749ee4f5473c87f692b93bebb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3d9eb180fbe8828cce43bce4c370124685b205c3"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T12:19:11Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.3,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The AEGIS-128 AEAD is driven from the local crypto API \u2014 an unprivileged user reaches it directly via an AF_ALG/algif_aead socket, and in-kernel consumers (dm-crypt, xfrm ESP) are configured locally. A remote peer cannot itself supply input that reaches the failing allocation, so this is local.\nAC:L - The failure requires a memory allocation failure inside skcipher_walk, but the attacker can both force the allocating slow path on every walk step (by submitting scatterlists fragmented below the 16-byte chunksize) and induce the memory pressure, then retry the operation arbitrarily many times; the GFP_ATOMIC variant used by softirq consumers fails readily under attacker-generated load.\nPR:L - Binding an AF_ALG socket to \"aegis128\" and issuing encrypt requests requires only an unprivileged local account \u2014 no capability, and module autoload happens on the user's behalf.\nUI:N - The attacker triggers the encrypt/decrypt path entirely on their own; no victim action is needed.\nS:U - The faulty error handling and its consequences stay within the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - On the unchecked error path the encrypt call returns success without encrypting, so the \"ciphertext\" handed to the caller is the raw plaintext (in-place operations) or stale kernel buffer contents (out-of-place, e.g. dm-crypt/ESP buffers), disclosing data that was supposed to be protected to disk, network peers, or backups.\nI:H - The kernel reports a successful AEAD operation while producing unencrypted, partially encrypted, or stale output with a mismatched tag, so data written to encrypted storage or an encrypted tunnel is silently wrong and cannot be distinguished from valid output by the caller.\nA:L - No kernel crash, hang, or corruption occurs; the impact is that the silently bad ciphertext/tag causes downstream rejection \u2014 dropped IPsec packets, I/O errors on integrity-protected volumes, and unrecoverable stored blocks \u2014 which is a limited interruption rather than a full loss of availability."
    }
  }
}