{
  "cveId": "CVE-2024-26706",
  "url": "https://patchblox.com/security/cve/CVE-2024-26706",
  "summary": "CVE-2024-26706 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-26706, released April 3, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "parisc: Fix random data corruption from exception handler",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  parisc: Fix random data corruption from exception handler  The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd().  To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the \u0022%r\u0022 prefix), which the GNU assembler can not convert to an integer.  This patch takes another, better and more flexible approach: We extend the __ex_table (which is out of the execution path) by one 32-word. In this word we tell the compiler to insert the assembler instruction \u0022or %r0,%r0,%reg\u0022, where %reg references the register which the compiler choosed for the error return code. In case of an access failure, the fault handler finds the __ex_table entry and can examine the opcode. The used register is encoded in the lowest 5 bits, and the fault handler can then store -EFAULT into this register.  Since we extend the __ex_table to 3 words we can\u0027t use the BUILDTIME_TABLE_SORT config option any longer.",
  "published": "2024-04-03T15:15:53Z",
  "severity": "Moderate",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "cwe": "Out-of-bounds Write",
  "epss": 0.00266,
  "epssPercentile": 0.18572,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26706",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.82-1",
      "fix": "DEBIAN-CVE-2024-26706",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-26706",
      "released": "2024-04-03T15:15:53Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.7.7-1",
      "fix": "DEBIAN-CVE-2024-26706",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-26706",
      "released": "2024-04-03T15:15:53Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.7.7-1",
      "fix": "DEBIAN-CVE-2024-26706",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-26706",
      "released": "2024-04-03T15:15:53Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}