{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72375",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72375"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "afs: Fix reinitialisation of the inode, in particular ->lock_work",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Fix reinitialisation of the inode, in particular ->lock_work\n\nIt seems that initalising afs_vnode::lock_work a single time in the slab's\ninit function isn't sufficient for work_structs.  This results in the\nDEBUG_OBJECTS debugging stuff producing a warning occasionally when running\nthe generic/131 xfstest:\n\n ODEBUG: activate not available (active state 0) object: 0000000016d8760f object type: work_struct hint: afs_lock_work+0x0/0x220\n WARNING: lib/debugobjects.c:629 at debug_print_object+0x4b/0x90, CPU#3: locktest/7695\n ...\n CPU: 3 UID: 0 PID: 7695 Comm: locktest Tainted: G S                  7.1.0-build3+ #2771 PREEMPT\n ...\n RIP: 0010:debug_print_object+0x65/0x90\n ...\n Call Trace:\n  <TASK>\n  ? __pfx_afs_lock_work+0x10/0x10\n  debug_object_activate+0x122/0x170\n  insert_work+0x25/0x60\n  __queue_work+0x2e0/0x340\n  queue_delayed_work_on+0x48/0x70\n  afs_fl_release_private+0x57/0x70\n  locks_release_private+0x5c/0xa0\n  locks_free_lock+0xe/0x20\n  posix_lock_inode+0x55f/0x5b0\n  locks_lock_inode_wait+0x81/0x140\n  ? file_write_and_wait_range+0x50/0x70\n  afs_lock+0xcd/0x110\n  fcntl_setlk+0x10d/0x260\n  do_fcntl+0x24e/0x5b0\n  __do_sys_fcntl+0x6a/0x90\n  do_syscall_64+0x11e/0x310\n  entry_SYSCALL_64_after_hwframe+0x71/0x79\n\nFix this by reinitialising ->lock_work after allocating an inode.\n\nAlso, flush ->lock_work when the inode is being evicted to make sure it's\nnot still running.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "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-2026-72375"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/63d3f283858fae097fb09ddd4ce46bb0bc1f9d01"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5597fbd1e7c161914f20315a726e54025b0fdadb"
    }
  ],
  "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": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The bug is reached only via the local VFS file-locking path (fcntl/F_SETLK/F_SETLKW \u2192 afs_lock \u2192 afs_fl_release_private \u2192 queue_delayed_work on vnode->lock_work), not from inbound AFS/RxRPC network packet handling.\nAC:L - An attacker can reliably drive the fault by cycling POSIX locks and inode eviction/reuse on AFS files they control; both sides of the workqueue/slab race are attacker-influenced and freely retryable, matching the intermittent generic/131 locktest reproducer.\nPR:L - On the highest-impact deployment (enterprise/university hosts with AFS already mounted), any unprivileged local user who can open files on that mount can trigger fcntl locking without real root or CAP_SYS_ADMIN in the init namespace.\nUI:N - Exploitation requires no action by another user; the attacker directly issues fcntl lock/unlock operations on file descriptors they hold on the shared AFS mount.\nS:U - Impact is confined to kernel memory corruption and privilege escalation within the same kernel security boundary; this is not a VM escape, IOMMU bypass, or cross-authority sandbox breakout.\nC:H - Stale lock_work reuse and eviction without flush_delayed_work() can leave afs_lock_work operating on freed/reallocated afs_vnode slab memory, a classic use-after-free that can disclose or corrupt adjacent kernel heap contents.\nI:H - Corrupting or re-queuing a stale delayed_work can corrupt workqueue lists and attacker-controlled vnode fields, providing primitives consistent with arbitrary kernel write and control-flow hijack, not merely a benign warning.\nA:H - Invalid work_struct state triggers kernel warnings/oops in testing and can panic the system when deferred lock work runs against an evicted inode or poisoned slab object during normal lock release."
    }
  }
}