CVE-2024-27367
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Samsung Mobile Processor Exynos Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsi_rx_scan_ind(), there is no input validation check on a length coming from userspace, which can lead to integer overflow and a potential heap over-read.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA missing input validation vulnerability in the slsi_rx_scan_ind() function allows a local attacker to supply a malicious length value from userspace, causing an integer overflow that leads to heap over-read. This affects multiple Samsung Exynos mobile and wearable processors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Exynos processor modelCheck the system's processor/hardware information to determine if it uses a Samsung Exynos chip (e.g., check /proc/cpuinfo, dmesg, or system information utilities for Exynos 980, 850, 1080, 1280, 1380, 1330, 1480, or W920)Affected if The device uses any of the affected Exynos models: 980, 850, 1080, 1280, 1380, 1330, 1480, or W920
-
Verify the slsi_rx_scan_ind function exists in firmwareExamine the firmware or kernel module binary for the presence of the slsi_rx_scan_ind symbol (using tools like nm, objdump, or firmware analysis tools)Affected if The slsi_rx_scan_ind function is present in the firmware or related kernel modules
-
Check if Wi-Fi or scanning functionality is enabledDetermine if the device has Wi-Fi scanning capabilities enabled (check system services, wlan driver modules, or scan-related kernel configurations)Affected if Wi-Fi scanning functionality and the associated userspace interface are present and accessible to local users
-
Verify userspace input path to the vulnerable functionInspect the firmware or kernel driver code to confirm that slsi_rx_scan_ind accepts length parameters directly from userspace without proper validationAffected if The slsi_rx_scan_ind function accepts a userspace-provided length value without bounds checking
A device is affected if it uses any of the listed Exynos processors (980, 850, 1080, 1280, 1380, 1330, 1480, W920) and contains the vulnerable slsi_rx_scan_ind function with an unvalidated userspace length input path.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Samsung firmware updates for affected Exynos processors when available. Samsung must add proper bounds checking on the userspace length parameter in slsi_rx_scan_ind() to prevent integer overflow.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27367 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data