CVE-2023-54105
published 2025-12-24CVE-2023-54105: In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family in isotp_bind() Add missing check to block non-AF_CAN…
PriorityP422
EPSS
0.18%
8.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10)
^^^^
This has no funtional impact but the userspace should be notified about
the wrong address family field content.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.20-1 (bookworm) | linux 6.1.20-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= e057dd3fc20ffb3d7f150af46542a51b59b90127 < de3c02383aa678f6799402ac47fdd89cf4bfcaa9 | de3c02383aa678f6799402ac47fdd89cf4bfcaa9 |
| linux | linux | >= e057dd3fc20ffb3d7f150af46542a51b59b90127 < 2fc6f337257f4f7c21ecff429241f7acaa6df4e8 | 2fc6f337257f4f7c21ecff429241f7acaa6df4e8 |
| linux | linux | >= e057dd3fc20ffb3d7f150af46542a51b59b90127 < 9427584c2f153d0677ef3bad6f44028c60d728c4 | 9427584c2f153d0677ef3bad6f44028c60d728c4 |
| linux | linux | >= e057dd3fc20ffb3d7f150af46542a51b59b90127 < dd4faace51e41a82a8c0770ee0cc26088f9d9d06 | dd4faace51e41a82a8c0770ee0cc26088f9d9d06 |
| linux | linux | >= e057dd3fc20ffb3d7f150af46542a51b59b90127 < c6adf659a8ba85913e16a571d5a9bcd17d3d1234 | c6adf659a8ba85913e16a571d5a9bcd17d3d1234 |
| linux | linux_kernel | >= 0 < 5.10.205-1 | 5.10.205-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 5.10.0 < 5.10.200 | 5.10.200 |
| linux | linux_kernel | >= 5.11.0 < 5.15.138 | 5.15.138 |
| linux | linux_kernel | >= 5.16.0 < 6.1.16 | 6.1.16 |
| linux | linux_kernel | >= 6.2.0 < 6.2.3 | 6.2.3 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
can: isotp: check CAN address family in isotp_bind()
osv·2025-12-24
CVE-2023-54105 can: isotp: check CAN address family in isotp_bind()
can: isotp: check CAN address family in isotp_bind()
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10)
^^^^
This has no funtional impact but the userspace should be notified about
the wrong address family field content.
GHSA
GHSA-pg9h-x33j-cfq7: In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block
ghsa_unreviewed·2025-12-24
CVE-2023-54105 GHSA-pg9h-x33j-cfq7: In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10)
^^^^
This has no funtional impact but the userspace should be notified about
the wrong address family field content.
OSV
CVE-2023-54105: In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family in isotp_bind() Add missing check to block no
osv·2025-12-24
CVE-2023-54105 CVE-2023-54105: In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family in isotp_bind() Add missing check to block no
In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field: bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the userspace should be notified about the wrong address family field content.
Red Hat
kernel: can: isotp: check CAN address family in isotp_bind()
vendor_redhat·2025-12-24
CVE-2023-54105 CWE-1287 kernel: can: isotp: check CAN address family in isotp_bind()
kernel: can: isotp: check CAN address family in isotp_bind()
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10)
^^^^
This has no funtional impact but the userspace should be notified about
the wrong address family field content.
A missing input validation was found in the Linux kernel's CAN ISO-TP protocol implementation. The isotp_bind() function does not verify that the address family in the sockaddr structure is AF_CAN. This allows bind calls with incorrect address
Debian
CVE-2023-54105: linux - In the Linux kernel, the following vulnerability has been resolved: can: isotp:...
vendor_debian·2023
CVE-2023-54105 CVE-2023-54105: linux - In the Linux kernel, the following vulnerability has been resolved: can: isotp:...
In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field: bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the userspace should be notified about the wrong address family field content.
Scope: local
bookworm: resolved (fixed in 6.1.20-1)
bullseye: resolved (fixed in 5.10.205-1)
forky: resolved (fixed in 6.1.20-1)
sid: resolved (fixed in 6.1.20-1)
trixie: resolved (fixed in 6.1.20-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2023-54105 kernel: can: isotp: check CAN address family in isotp_bind()
bugzilla·2025-12-24
CVE-2023-54105 CVE-2023-54105 kernel: can: isotp: check CAN address family in isotp_bind()
CVE-2023-54105 kernel: can: isotp: check CAN address family in isotp_bind()
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10)
^^^^
This has no funtional impact but the userspace should be notified about
the wrong address family field content.
Discussion:
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025122411-CVE-2023-54105-fbe5@gregkh/T
Wiz
CVE-2023-54105 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54105 CVE-2023-54105 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54105 :
Linux Kernel vulnerability analysis and mitigation
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10)
^^^^
This has no funtional impact but the userspace should be notified about
the wrong address family field content.
Source : NVD
Published December 24, 2025
CNA Score N/A
Affected Technologies
Linux Kernel
Linux Debian
Has Public Exploit No
Has CISA KEV Exploit No
CISA KEV Release Date N/A
CISA KEV Due Date N/A
Exploitation Probabili
https://git.kernel.org/stable/c/2fc6f337257f4f7c21ecff429241f7acaa6df4e8https://git.kernel.org/stable/c/9427584c2f153d0677ef3bad6f44028c60d728c4https://git.kernel.org/stable/c/c6adf659a8ba85913e16a571d5a9bcd17d3d1234https://git.kernel.org/stable/c/dd4faace51e41a82a8c0770ee0cc26088f9d9d06https://git.kernel.org/stable/c/de3c02383aa678f6799402ac47fdd89cf4bfcaa9
2025-12-24
Published