Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31664xfrm: clear trailing padding in build_polexpire()

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: clear trailing padding in build_polexpire() build_expire() clears the trailing padding bytes of struct xfrm_user_expire after setting the hard field via memset_after(), but the analogous function build_polexpire() does not do this for struct xfrm_user_polexpire. The padding bytes after the __u8 hard field are left uninitialized from the heap allocation, and are then sent to userspace via netlink multicast to XFRMNLGRP_EXPIRE listeners, leaking kernel heap memory contents. Add the missing memset_after() call, matching build_expire().

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31664, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a5127501c8d30b5728791b1e340284ca5c9cc4bd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e6f4ffe8596947a595c9544e73a73adcb0568b88
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ac6985903db047eaff54db929e4bf6b06782788e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c221ed63a2769a0af8bd849dfe25740048f34ef4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < eda30846ea54f8ed218468e5480c8305ca645e37
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b1dfd6b27df35ef4f87825aa5f607378d23ff0f2
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e1af65c669ebb1666c54576614c01a7f9ffcfff6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 71a98248c63c535eaa4d4c22f099b68d902006d0
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.169 – ≤ 6.1.*
    • unaffected 6.6.135 – ≤ 6.6.*
    • unaffected 6.12.82 – ≤ 6.12.*
    • unaffected 6.18.23 – ≤ 6.18.*
    • unaffected 6.19.13 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31664 badge
[![CVE-2026-31664](https://cveledger.app/badge/CVE-2026-31664.svg)](https://cveledger.app/cve/CVE-2026-31664)

Record last updated .