LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38560: scsi: bfa: Ensure the copied buf is NUL terminated

In the Linux kernel, the following vulnerability has been resolved: scsi: bfa: Ensure the copied buf is NUL terminated Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from userspace to that buffer. Later, we use sscanf on this buffer but we don't ensure that the string is terminated inside the buffer, this can lead to OOB read when using sscanf. Fix this issue by using memdup_user_nul instead of memdup_user.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38560 is a Linux kernel flaw in the bfa SCSI driver. A userspace-provided buffer was copied without guaranteed string termination, then parsed as a string, allowing an out-of-bounds read. The public record does not provide CVSS, confirmed impact beyond OOB read, or evidence of active exploitation.

Executive priority

Treat this as routine kernel patch management unless bfa is used on important storage infrastructure. There is no provided evidence of exploitation or severity scoring, but kernel memory safety issues should not linger on systems with local user access or storage-adapter exposure.

Technical view

The bfa driver allocated an nbytes-sized kernel buffer, copied nbytes from userspace, then passed it to sscanf without ensuring NUL termination. The kernel fix replaces memdup_user with memdup_user_nul, ensuring the copied buffer is terminated before parsing.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds that include and use the bfa SCSI driver. Appliance or embedded products may inherit exposure through their vendor kernel. The supplied data lists affected Linux versions and multiple stable backport commits, but not every downstream package status.

Exploitation context

The source bundle marks this CVE as not in KEV and provides no cited evidence of active exploitation. The described weakness requires a reachable userspace-to-kernel parsing path in the bfa driver. No exploit prerequisites, public exploit, or weaponized activity are established in the provided sources.

Researcher notes

The evidence supports an out-of-bounds read caused by missing NUL termination before sscanf. Impact characterization is limited: the bundle does not state privilege escalation, remote attack surface, information disclosure scope, crashability, or exploit maturity. Downstream exposure must be validated per kernel build and vendor backport status.

Mitigation direction

  • Apply Linux stable or distribution kernel updates containing the referenced bfa fix.
  • For Debian LTS systems, review and apply the June 2024 security update.
  • Check vendor advisories for appliances or products using downstream Linux kernels.
  • Confirm whether the bfa driver is required before changing driver availability.
  • Track vendor guidance where no direct patch status is listed.

Validation and detection

  • Inventory Linux kernel versions and compare against fixed stable branch releases.
  • Check whether the bfa driver is present, loaded, or required on affected hosts.
  • Verify distro advisory status for each deployed kernel package.
  • Confirm patched source includes memdup_user_nul in the affected bfa parsing path.
  • Review vendor notices for embedded or managed products using Linux kernels.
Prepared
Confidence
medium
Sources
12

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-2024-38560 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
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cb, 9f30b674759b9a2da25aefe25d885161d8a911cbunaffected
LinuxLinux3.19, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

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