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-43209minix: Add required sanity checking to minix_check_superblock()

Description

In the Linux kernel, the following vulnerability has been resolved: minix: Add required sanity checking to minix_check_superblock() The fs/minix implementation of the minix filesystem does not currently support any other value for s_log_zone_size than 0. This is also the only value supported in util-linux; see mkfs.minix.c line 511. In addition, this patch adds some sanity checking for the other minix superblock fields, and moves the minix_blocks_needed() checks for the zmap and imap also to minix_check_super_block(). This also closes a related syzbot bug report.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 5 days 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-43209, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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 98% of all CVEs (17 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 – < a051ecf5c5b0387840dc210413ed3bc7fbdaa69c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d791c544efd6b9c944b43cf7f502e5bcb02fb941
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 66c7c239c65341f99ae388d4d53dc9df2bcb9925
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2bb588cede1c1969e49c0a2822c8cb8b346b7682
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f57ccd4657c7f082dc47e5b9e18a883bb5f9118f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 31fefc18096cdc5549cfa54964d90e0b3229aedc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1efc128ee4adbc23e082715425ff895449d233bc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8c97a6ddc95690a938ded44b4e3202f03f15078c
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .