null_blk: free global tag_set on init error path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: null_blk: free global tag_set on init error path If shared_tags is enabled, null_setup_tagset() allocates the global tag_set via null_init_global_tag_set(). If device creation later fails, err_dev destroys the default devices and calls unregister_blkdev(), but never frees the global tag_set. Since module init failed, null_exit() is never invoked, so the global tag_set's tags and maps are permanently leaked. Free the global tag_set in err_dev, matching null_exit() which does if (tag_set.ops) blk_mq_free_tag_set(&tag_set).
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 82f402fefa50f1675bf918bcd009981bd6b30ac8 · fixed in 0b2faa330184340d9418ad2c627c2ae881772e33; From 82f402fefa50f1675bf918bcd009981bd6b30ac8 · fixed in 665c94554ff0d5d88caae7f40c16c8e0a3369eda; From 82f402fefa50f1675bf918bcd009981bd6b30ac8 · fixed in 2882e1450fa4597811a951196e07553ea134eb31; From 82f402fefa50f1675bf918bcd009981bd6b30ac8 · fixed in 2b59484ac1e64dd78dbe8c6140891c6308085a75; From 82f402fefa50f1675bf918bcd009981bd6b30ac8 · fixed in 081cf37e8a0e00cd91d6df53172c9d928790a798; From 82f402fefa50f1675bf918bcd009981bd6b30ac8 · fixed in 5a1c5ff3a49ba93a1fd0b70537e7a0164071760d
- Linux Linux
4.13
- KernelLinux
From 4.13.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6