CVE-2024-46676: Linux kernel · nfc: pn533: Add poll mod list filling check
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1135.145~18.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 11:13 UTC
- Patch
- Available – fixed in 5.4.0-1135.145~18.04.1, 5.4.0-1140.147~18.04.1, 5.4.0-1139.148~18.04.1 +75
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.
Patches and advisories
- ubuntu.com/security/notices/USN-7088-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7119-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7123-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7144-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7154-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7155-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkeoppkg:deb/ubuntu/linux-gkeop?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Add poll mod list filling check In case of im_protocols value is 1 and tm_protocols value is 0 this combination successfully passes the check 'if (!im_protocols && !tm_protocols)' in the nfc_start_poll(). But then after pn533_poll_create_mod_list() call in pn533_start_poll() poll mod list will remain empty and dev->poll_mod_count will remain 0 which lead to division by zero. Normally no im protocol has value 1 in the mask, so this combination is not expected by driver. But these protocol values actually come from userspace via Netlink interface (NFC_CMD_START_POLL operation). So a broken or malicious program may pass a message containing a "bad" combination of protocol parameter values so that dev->poll_mod_count is not incremented inside pn533_poll_create_mod_list(), thus leading to division by zero. Call trace looks like: nfc_genl_start_poll() nfc_start_poll() ->start_poll() pn533_start_poll() Add poll mod list filling check. Found by Linux Verification Center (linuxtesting.org) with SVACE.
References
- ubuntu.com/security/CVE-2024-46676 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-46676 (opens in a new tab)
- git.kernel.org/linus/febccb39255f9df35527b88c953b2e0deae50e53 (opens in a new tab)
- git.kernel.org/stable/c/c5e05237444f32f6cfe5d907603a232c77a08b31 (opens in a new tab)
- git.kernel.org/stable/c/8ddaea033de051ed61b39f6b69ad54a411172b33 (opens in a new tab)
- git.kernel.org/stable/c/7535db0624a2dede374c42040808ad9a9101d723 (opens in a new tab)
- git.kernel.org/stable/c/7ecd3dd4f8eecd3309432156ccfe24768e009ec4 (opens in a new tab)
- git.kernel.org/stable/c/56ad559cf6d87f250a8d203b555dfc3716afa946 (opens in a new tab)
- git.kernel.org/stable/c/64513d0e546a1f19e390f7e5eba3872bfcbdacf5 (opens in a new tab)
- git.kernel.org/stable/c/febccb39255f9df35527b88c953b2e0deae50e53 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7119-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7123-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7144-1 (opens in a new tab)