Dear list,

quick question:

Does Kernel 6.1.190-1 (build date 2026-10-16) from bookworm-security positively fix CVE-2026-98432?

I updated to this kernel on one of my bookworm boxes, and initially only wanted to scan other hosts, to test for vulnerability and effectiveness of firewall rules.

I used "Alucard0x1" 's poc-Project for that:
https://github.com/Alucard0x1/cve-2026-98432

To get a baseline of how the result for a fixed system should look, I started a local scan of this patched system and got - to my surprise - vulnerable as a result.

The tool returned 10 frames that seems to contain data from other memory allocations in 180s (410000 packets tried). I obviously expected 0, which seems to be the norm for fixed kernels according to the author...

[!] UAF ORACLE HIT #10 at attempt sport=63481 (expected magic 99c1d106 tag c39b8b5c)     tcp 127.0.0.1:9000 -> 127.0.0.1:63481 seq=254469ff ack=d293e20a flags=0x12     SYN-ACK echoed magic d0c3b89a tag 8a99e2c0, belongs to another allocation (expected 99c1d106)
    ip options:
    0000  44 28 11 00 03 5a 21 64 03 5a 9c 67 03 5a 9c 67 D(...Z!d.Z.g.Z.g
    0010  d0 c3 b8 9a 8a 99 e2 c0 00 00 00 00 00 00 00 00 ................
    0020  00 00 00 00 00 00 00 00 ........
    frame saved to /tmp/proof.pcap (#10)
uname -a
Linux ***** 6.1.0-54-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.190-1 (2026-10-16) x86_64 GNU/Linux


I'm operating rather at a surface level atm, so haven't had a look at how exactly this tool works and if something else is amiss here, but packet corruption is (it being loopback) out of the question here, I guess?

Would be grateful for a bit of input on this.


Greetings,
Robin

Attachment: smime.p7s
Description: Kryptografische S/MIME-Signatur

Reply via email to