{
  "cveId": "CVE-2026-31705",
  "url": "https://patchblox.com/security/cve/CVE-2026-31705",
  "summary": "CVE-2026-31705 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-31705, released May 15, 2026. It is not reported as exploited. Patch Radar priority: Urgent.",
  "title": "ksmbd: fix out-of-bounds write in smb2_get_ea() EA alignment",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix out-of-bounds write in smb2_get_ea() EA alignment  smb2_get_ea() applies 4-byte alignment padding via memset() after writing each EA entry. The bounds check on buf_free_len is performed before the value memcpy, but the alignment memset fires unconditionally afterward with no check on remaining space.  When the EA value exactly fills the remaining buffer (buf_free_len == 0 after value subtraction), the alignment memset writes 1-3 NUL bytes past the buf_free_len boundary. In compound requests where the response buffer is shared across commands, the first command (e.g., READ) can consume most of the buffer, leaving a tight remainder for the QUERY_INFO EA response. The alignment memset then overwrites past the physical kvmalloc allocation into adjacent kernel heap memory.  Add a bounds check before the alignment memset to ensure buf_free_len can accommodate the padding bytes.  This is the same bug pattern fixed by commit beef2634f81f (\u0022ksmbd: fix potencial OOB in get_file_all_info() for compound requests\u0022) and commit fda9522ed6af (\u0022ksmbd: fix OOB write in QUERY_INFO for compound requests\u0022), both of which added bounds checks before unconditional writes in QUERY_INFO response handlers.",
  "published": "2026-05-01T14:16:20Z",
  "severity": "Critical",
  "cvss": 9.8,
  "cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00398,
  "epssPercentile": 0.34269,
  "priority": "Urgent",
  "priorityTier": 2,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-31705",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.176-1",
      "fix": "DEBIAN-CVE-2026-31705",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-31705",
      "released": "2026-05-15T16:01:09Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.85-1",
      "fix": "DEBIAN-CVE-2026-31705",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-31705",
      "released": "2026-05-15T16:01:09Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.3-1",
      "fix": "DEBIAN-CVE-2026-31705",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-31705",
      "released": "2026-05-15T16:01:09Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T01:18:40Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}