CVE-2026-72155None▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: swp: Improve locking user experience In the case of the first block being locked (or the few first blocks), if the user want to fully unlock the device i…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
In the Linux kernel, the following vulnerability has been resolved:
mtd: spi-nor: swp: Improve locking user experience
In the case of the first block being locked (or the few first blocks), if the user want to fully unlock the device it has two possibilities:
It fails because the conditions "can_be_top" and "can_be_bottom" are true. Indeed, in this case, we unlock everything, so the TB bit does not matter. However in the current implementation, use_top would be true (as this is the favourite option) and lock_len, which in practice should be reduced down to 0, is set to "nor->params->size - (ofs + len)" which is a positive number. This is wrong.
An easy way is to simply add an extra condition. In the unlock() path, if we can achieve the same result from both sides, it means we unlock everything and lock_len must simply be 0. A comment is added to clarify that logic.
Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < 23c285be8f6fcde9088fe12bb69c701d46696be1Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < a6fd2145c73b80bb6a5eed7355a4f63597d712d9Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038aLinux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < dc341272cf8e15a2c511db3c4df5dab8adf70ad0Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < 6110ab5ffd84e8daa654652446a03ce2f77580a7Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < c0806df5cf806545160f3fdac3c888926ceac557Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < 12d4d69221159e6d0e72400ec81195d691169b53Linux >= 3dd8012a8eeb3702fa17450ec1a16a3f38af138d < e1d456b26bf23e30db305a6184e8abd9ab68bbf2Linux 4.6Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses