Race Condition Affecting kernel-livepatch-6.12.103-127.188 package, versions <1:1.0-0.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.2% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNELLIVEPATCH612103127188-19474623
  • published1 Sept 2026
  • disclosed10 Aug 2026

Introduced: 10 Aug 2026

CVE-2026-68396  (opens in a new tab)
CWE-366  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-livepatch-6.12.103-127.188 to version 1:1.0-0.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2110.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6.12.103-127.188 package and not the kernel-livepatch-6.12.103-127.188 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

scsi: core: wake eh reliably when using scsi_schedule_eh

Drivers which use the scsi_schedule_eh function to run the error handler currently risk the error handler thread never waking once all commands are timed out or inactive. There is no enforced memory order between setting the host into error recovery state and counting busy commands. This can result in a race with scsi_dec_host_busy where neither CPU sees both conditions of all commands inactive and the host error state to request waking the error handler.

To fix this, run the scsi_schedule_eh's scsi_eh_wakeup from a new work item which will use rcu to ensure scsi_schedule_eh's call to scsi_host_busy will occur after the error state is globally visible and will be seen by any current scsi_dec_host_busy callers.

CVSS Base Scores

version 3.1