CVE-2026-98171 Affecting kernel6.18-debuginfo package, versions <1:6.18.54-121.166.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.51% (42nd 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-KERNEL618DEBUGINFO-21417466
  • published22 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-98171  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel6.18-debuginfo to version 1:6.18.54-121.166.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3192.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel6.18-debuginfo package and not the kernel6.18-debuginfo 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:

smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs

Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:

  • Clear next_buffer after assigning it to server->bigbuf. A stale next_buffer pointer can lead to a use-after-free on subsequent error paths.
  • Update pdu_length to the decrypted plaintext size (buf_size). Using the pre-decryption length allows NextCommand to point into stale ciphertext residue.
  • Reject next_cmd values smaller than MID_HEADER_SIZE(server).
  • Fix an integer overflow in the upper bound check by verifying pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the trailing slice is large enough for a header.