{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-31676",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-31676"
  ],
  "published": "2026-04-25T08:46:52Z",
  "summary": "rxrpc: only handle RESPONSE during service challenge",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: only handle RESPONSE during service challenge\n\nOnly process RESPONSE packets while the service connection is still in\nRXRPC_CONN_SERVICE_CHALLENGING. Check that state under state_lock before\nrunning response verification and security initialization, then use a local\nsecured flag to decide whether to queue the secured-connection work after\nthe state transition. This keeps duplicate or late RESPONSE packets from\nre-running the setup path and removes the unlocked post-transition state\ntest.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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": "6.1.175",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-31676"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a1a8efde03a40b6c658d580e96644d9b9a2a0d3a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6c3a0fbdafef8316e34ae22333e317a341e737cd"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0afdfd4941c1b60a1f5c361760daa970edca60cd"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a6bcf8010af093fe04f7100562e9542ab7882585"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/29b44d904dceb832be880def08b8cb17a0aba91c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d0035e634dae83237ab7f5681eb52b2f65d0ceb8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/03fd2ef73cb4ffd0af100a95b634af54f474414e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c43ffdcfdbb5567b1f143556df8a04b4eeea041c"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.5,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - RxRPC is a UDP-based network protocol, and the vulnerable RESPONSE handling is reached by packets sent to a listening AF_RXRPC service endpoint.\nAC:L - The attacker controls the packet timing and can send duplicate or late RESPONSE packets on a service connection; no uncontrollable race or special memory layout is required to trigger repeated setup processing.\nPR:N - The packet path is reached during the service-side authentication handshake before local privileges are required on the target, and a remote peer can exercise it by sending RxRPC protocol packets to the exposed service.\nUI:N - No victim user action is needed once an RxRPC service is listening; packet processing occurs in the kernel receive path.\nS:U - The impact remains within the kernel and the affected RxRPC service security authority, with no VM, sandbox, or separate security-scope escape.\nC:N - The bug re-runs connection security setup and leaks/replaces connection security objects, but I found no direct information disclosure or arbitrary read primitive.\nI:N - The reachable effect is improper repeated security initialization rather than attacker-controlled memory corruption or arbitrary modification of protected data.\nA:H - Repeated late or duplicate RESPONSE packets can repeatedly allocate and leak connection security state and disrupt/abort RxRPC connections, making kernel or service-level denial of service a reasonable impact."
    }
  }
}