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-46128ipmi: Check event message buffer response for bad data

Description

In the Linux kernel, the following vulnerability has been resolved: ipmi: Check event message buffer response for bad data The event message buffer response data size got checked later when processing, but check it right after the response comes back. It appears some BMCs may return an empty message instead of an error when fetching events. There are apparently some new BMCs that make this error, so we need to compensate.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-46128, by who scored it
Scored byCVSSScoreVector
NVDNVD · Undergoing Analysis3.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.13% · top 97% of all CVEs (13 Nov 2026)
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 – < cf1ef30c42a7079e5bad863cd01c52aa3a17c3ac
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 474e53d4397087913a5b9c9eb90fa068da4808bf
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 01f8387fa5b796f13cf50014c171f6da7abc46ea
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2418e4b21fb1355504d095da5d5f0a210564a43d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7f7ada72c07a83b46045ddfeee526bd9e2e3c8f0
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 42432b579a594b66ac32e5e7b7c26e6bc578ec89
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 24269264c3d59a49eb09b10af2c75b14f2931482
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 36920f30e78e69df01f9691c470b6f3ba8aebf98
  • 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.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.88 – ≤ 6.12.*
    • unaffected 6.18.30 – ≤ 6.18.*
    • unaffected 7.0.7 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .