Bug 2393534 (CVE-2025-39694) - CVE-2025-39694 kernel: s390/sclp: Fix SCCB present check
Summary: CVE-2025-39694 kernel: s390/sclp: Fix SCCB present check
Keywords:
Status: NEW
Alias: CVE-2025-39694
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-05 18:04 UTC by OSIDB Bzimport
Modified: 2025-10-16 08:15 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:16398 0 None None None 2025-09-23 00:36:29 UTC
Red Hat Product Errata RHSA-2025:16904 0 None None None 2025-09-29 07:48:03 UTC

Description OSIDB Bzimport 2025-09-05 18:04:50 UTC
In the Linux kernel, the following vulnerability has been resolved:

s390/sclp: Fix SCCB present check

Tracing code called by the SCLP interrupt handler contains early exits
if the SCCB address associated with an interrupt is NULL. This check is
performed after physical to virtual address translation.

If the kernel identity mapping does not start at address zero, the
resulting virtual address is never zero, so that the NULL checks won't
work. Subsequently this may result in incorrect accesses to the first
page of the identity mapping.

Fix this by introducing a function that handles the NULL case before
address translation.

Comment 5 errata-xmlrpc 2025-09-23 00:36:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:16398 https://access.redhat.com/errata/RHSA-2025:16398

Comment 6 errata-xmlrpc 2025-09-29 07:48:02 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:16904 https://access.redhat.com/errata/RHSA-2025:16904


Note You need to log in before you can comment on or make changes to this bug.