LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53703: HID: amd_sfh: Fix for shift-out-of-bounds

In the Linux kernel, the following vulnerability has been resolved: HID: amd_sfh: Fix for shift-out-of-bounds Shift operation of 'exp' and 'shift' variables exceeds the maximum number of shift values in the u32 range leading to UBSAN shift-out-of-bounds. ... [ 6.120512] UBSAN: shift-out-of-bounds in drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50 [ 6.120598] shift exponent 104 is too large for 64-bit type 'long unsigned int' [ 6.120659] CPU: 4 PID: 96 Comm: kworker/4:1 Not tainted 6.4.0amd_1-next-20230519-dirty #10 [ 6.120665] Hardware name: AMD Birman-PHX/Birman-PHX, BIOS SFH_with_HPD_SEN.FD 04/05/2023 [ 6.120667] Workqueue: events amd_sfh_work_buffer [amd_sfh] [ 6.120687] Call Trace: [ 6.120690] <TASK> [ 6.120694] dump_stack_lvl+0x48/0x70 [ 6.120704] dump_stack+0x10/0x20 [ 6.120707] ubsan_epilogue+0x9/0x40 [ 6.120716] __ubsan_handle_shift_out_of_bounds+0x10f/0x170 [ 6.120720] ? psi_group_change+0x25f/0x4b0 [ 6.120729] float_to_int.cold+0x18/0xba [amd_sfh] [ 6.120739] get_input_rep+0x57/0x340 [amd_sfh] [ 6.120748] ? __schedule+0xba7/0x1b60 [ 6.120756] ? __pfx_get_input_rep+0x10/0x10 [amd_sfh] [ 6.120764] amd_sfh_work_buffer+0x91/0x180 [amd_sfh] [ 6.120772] process_one_work+0x229/0x430 [ 6.120780] worker_thread+0x4a/0x3c0 [ 6.120784] ? __pfx_worker_thread+0x10/0x10 [ 6.120788] kthread+0xf7/0x130 [ 6.120792] ? __pfx_kthread+0x10/0x10 [ 6.120795] ret_from_fork+0x29/0x50 [ 6.120804] </TASK> ... Fix this by adding the condition to validate shift ranges.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the AMD Sensor Fusion Hub HID driver. A bad shift calculation can exceed valid bounds, causing undefined-behavior sanitizer warnings in kernel code. The source confirms a code fix but does not describe real-world attacks, business impact, or a CVSS score.

Executive priority

Treat this as a targeted Linux kernel maintenance item, not a confirmed emergency. Prioritize affected AMD Linux endpoints, laptops, or embedded systems if they are business-critical or showing kernel stability warnings.

Technical view

The flaw is a shift-out-of-bounds condition in drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c during AMD SFH input report handling. The kernel fix adds validation for shift ranges. The public record lists Linux kernel versions and stable commits but does not provide exploitability details.

Likely exposure

Exposure appears limited to Linux systems using the AMD SFH HID driver on relevant AMD hardware and affected kernel builds listed in the CVE source. Non-AMD systems or kernels without this driver path are less likely to be exposed, but the source does not provide a complete product matrix.

Exploitation context

The source bundle does not show active exploitation, KEV listing, proof-of-concept availability, remote attackability, or privilege requirements. Evidence is limited to a kernel UBSAN trace and stable fix references.

Researcher notes

The record lacks CVSS, CWE, and exploitability analysis. The strongest evidence is the upstream kernel description and stable commits. Avoid assuming remote reachability or security impact beyond the documented undefined shift condition.

Mitigation direction

  • Inventory Linux systems with AMD SFH hardware or the amd_sfh driver enabled.
  • Apply distribution kernel updates that include the referenced Linux stable fixes.
  • If no package exists, follow vendor or distribution backport guidance.
  • Monitor kernel logs for amd_sfh shift-out-of-bounds UBSAN messages.

Validation and detection

  • Confirm running kernel versions against the CVE affected version data.
  • Check distribution changelogs for CVE-2023-53703 or referenced commit IDs.
  • Review dmesg or journal logs for amd_sfh UBSAN shift-out-of-bounds entries.
  • Verify updated kernels include shift range validation in the AMD SFH driver.
Prepared
Confidence
medium
Sources
5

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-53703 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
4Source 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
LinuxLinux93ce5e0231d79189be4d9e5f9295807b18941419, 93ce5e0231d79189be4d9e5f9295807b18941419, 93ce5e0231d79189be4d9e5f9295807b18941419unaffected
LinuxLinux6.0, 0, 6.1.40, 6.4.5, 6.5affected
Weakness

CWE details

No CWE listed

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