# CVE-2023-54105: can: isotp: check CAN address family in isotp_bind()

> A missing check in the Linux kernel CAN ISOTP module allows binding with incorrect address families, potentially leading to unexpected behavior or information leakage.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54105, DEBIAN-CVE-2023-54105, GHSA-pg9h-x33j-cfq7, ROOT-OS-UBUNTU-2204-CVE-2023-54105, ROOT-OS-UBUNTU-2404-CVE-2023-54105, UBUNTU-CVE-2023-54105

## What is CVE-2023-54105?

CVE-2023-54105 is a missing authorization vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2023-54105?


## How do I fix CVE-2023-54105?

Apply the vendor's patch.

## Is CVE-2023-54105 being exploited?

There is no known exploitation of CVE-2023-54105 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54105 and fix it if it is affected.

What it is: CVE-2023-54105 is a missing authorization vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54105 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54105/ (Markdown: https://insights.sbomify.com/CVE-2023-54105/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54105
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54105
- OSV: https://osv.dev/vulnerability/CVE-2023-54105

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54105/
Summaries are generated and may contain mistakes; the official description above is the record.