{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72462",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72462"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "apparmor: fix race in unix socket mediation when peer_path is used",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race in unix socket mediation when peer_path is used\n\nThe holding a reference to the peer_sk is not enough to ensure access\nto the peer sk path. Accessing the path outside of the state lock\nallows for a race with unix_release_sock(). Fix this by taking the\nstate lock and getting a reference to the path under lock.\n\nIdeally for connected sockets we would cache this information so we\ndon't have to take the lock here. But for now just fix the race.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.29-1+rpt1",
        "1:6.18.33-1+rpt1",
        "1:6.18.34-1+rpt1",
        "1:6.18.39-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-2712",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v6",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v7",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-2712",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v6",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v7",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-2712",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v6",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v7",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-2712",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v6",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v7",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v8",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.39-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.29-1+rpt1": {
            "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc",
            "upstream_version": "6.18.29",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.34-1+rpt1": {
            "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af",
            "upstream_version": "6.18.34",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.39-1+rpt1": {
            "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff",
            "upstream_version": "6.18.39",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-72462"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d8ea44f6090c087fe255d9512fb808574b4d88e8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d680472db98823d90fc91362910901e468269318"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b1aea2c1960771a276d7e68c7424168eccd0c3da"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - Exploitation requires local Unix domain socket syscalls (connect/read/write/close) that reach the AppArmor file_permission LSM hook on a connected PF_UNIX socket; there is no network packet or remote protocol path to this code.\nAC:L - The attacker controls both ends of the race by concurrently I/O'ing on an abstract/anonymous socket connected to a filesystem-bound peer while closing the peer socket, repeatedly timing read/write against peer teardown until the window is hit.\nPR:L - Any unprivileged local user can create and connect Unix sockets and trigger revalidation on confined workloads (snaps, containers, desktop services on AppArmor-enabled Ubuntu/Debian); no real-root or init-namespace capabilities are required.\nUI:N - Exploitation is fully attacker-driven through automated concurrent socket operations and does not require any victim user action such as opening files or mounting filesystems.\nS:C - Winning the race can bypass AppArmor Unix peer_path mediation (implicit allow when dentry is cleared) or corrupt kernel objects via dentry UAF, crossing the AppArmor confinement boundary that normally separates confined from unconfined authority.\nC:H - Use-after-free of the peer socket's dentry/inode during unix_fs_perm/aa_path_perm allows dereferencing freed kernel heap memory, which per kernel CVSS guidance for UAF enables arbitrary kernel memory disclosure primitives.\nI:H - The UAF on struct path/dentry/inode is heap memory corruption that can be leveraged for arbitrary kernel writes and control-flow hijack; the race can also silently bypass AppArmor peer filesystem permission enforcement.\nA:H - Dereferencing a released peer_path dentry in unix_fs_perm can cause kernel oops/panic; UAF during active socket I/O on production AppArmor-confined services (D-Bus, journald, snap apps) enables repeatable denial of service."
    }
  }
}
