LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54105: 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-54105 is a Linux kernel CAN ISO-TP socket issue where bind() accepted the wrong address family. The source says this has no functional impact, but userspace should receive an error for invalid input. No active exploitation is cited, and severity data is not provided.

Executive priority

Treat this as routine kernel hygiene unless CAN ISO-TP is material to the environment. No evidence provided supports emergency action, but patched kernels should be adopted through standard maintenance.

Technical view

In Linux kernel CAN ISO-TP, isotp_bind() missed a check blocking non-AF_CAN address families. Syzbot demonstrated a sockaddr of the expected size using AF_XDP instead of AF_CAN. Kernel stable commits add validation so invalid address family values are rejected.

Likely exposure

Exposure is likely limited to Linux systems with CAN ISO-TP functionality available. Practical business exposure appears low from the provided record, but teams should verify kernel versions and distribution backports.

Exploitation context

The bundle does not cite exploitation in the wild, and KEV is false. The described trigger came from syzbot fuzzing and is documented as having no functional impact.

Researcher notes

The key evidence is the missing AF_CAN validation in isotp_bind(). Impact evidence is narrow: the record explicitly says no functional impact. Version data is incomplete for distro kernels, so branch-specific vendor advisories matter.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fix.
  • Check Linux distribution advisories for backported fixes.
  • Disable or restrict unused CAN ISO-TP functionality where operationally feasible.
  • Track kernel package remediation through normal vulnerability management workflows.

Validation and detection

  • Inventory Linux kernel versions across systems using CAN or automotive interfaces.
  • Confirm whether vendor kernels include the referenced stable commits.
  • Review enabled kernel modules and socket CAN usage.
  • Prioritize validation on systems exposing CAN workloads or device testing environments.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54105 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe057dd3fc20ffb3d7f150af46542a51b59b90127, e057dd3fc20ffb3d7f150af46542a51b59b90127, e057dd3fc20ffb3d7f150af46542a51b59b90127, e057dd3fc20ffb3d7f150af46542a51b59b90127, e057dd3fc20ffb3d7f150af46542a51b59b90127unaffected
LinuxLinux5.10, 0, 5.10.200, 5.15.138, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.