Skip to main content
VulnerabilityPublished Updated

CVE-2026-98833: Linux kernel · mtd: core: call _get_device() with the master MTD

Source GCVE Database

0
Authoritative record:CVE-2026-98833

Not known to be exploited · fixed in f971f1c63cf71579258360a12bd185bc1cd1a043 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f971f1c63cf71579258360a12bd185bc1cd1a043, dc482a281a19a7d7e91ad1b2d551bb301c54d0e6, d94731cafa57e2c986ff391122d1494e5a3f3c3f +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 46b5889cc2c54bac7d7e727a44d28a298df23cef, < f971f1c63cf71579258360a12bd185bc1cd1a043
Fixed in
  • f971f1c63cf71579258360a12bd185bc1cd1a043
LinuxLinuxAffected
  • ≥ 46b5889cc2c54bac7d7e727a44d28a298df23cef, < dc482a281a19a7d7e91ad1b2d551bb301c54d0e6
Fixed in
  • dc482a281a19a7d7e91ad1b2d551bb301c54d0e6
LinuxLinuxAffected
  • ≥ 46b5889cc2c54bac7d7e727a44d28a298df23cef, < d94731cafa57e2c986ff391122d1494e5a3f3c3f
Fixed in
  • d94731cafa57e2c986ff391122d1494e5a3f3c3f
LinuxLinuxAffected
  • ≥ 46b5889cc2c54bac7d7e727a44d28a298df23cef, < 95c8f36293c22d450c371167ad4f9a5bbadc7539
Fixed in
  • 95c8f36293c22d450c371167ad4f9a5bbadc7539
LinuxLinuxAffected
  • ≥ 46b5889cc2c54bac7d7e727a44d28a298df23cef, < 12b31d1acd20b3185bb5f0748db0cf6874c8e9d1
Fixed in
  • 12b31d1acd20b3185bb5f0748db0cf6874c8e9d1
LinuxLinuxAffected
  • =5.7
Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to correctly pass the master MTD device to the _get_device() callback, resolving the issue. Users should apply the official kernel update containing this fix. Patch status is not explicitly stated in the input data, so verify with the Linux kernel vendor advisory for the exact fixed versions and update instructions.

Description

A vulnerability in the Linux kernel's MTD (Memory Technology Device) core component has been resolved. The issue involved incorrect handling of the master MTD device when calling the _get_device() callback, which affected gluebi partitions relying on container_of() with the master MTD. The fix ensures the master MTD is passed correctly to _get_device(), aligning with the behavior of _put_device().

References

Community reviews

Loading reviews…