Bug 2278337 (CVE-2024-26982)

Summary:	CVE-2024-26982 kernel: Squashfs: check the inode number is not the invalid value of zero
Product:	[Other] Security Response	Reporter:	Zack Miele <zmiele>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, vsroka, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel 6.8.8, kernel 6.9-rc5	Doc Type:	If docs needed, set a value
Doc Text:	A flaw was found in the squashfs module in the Linux kernel. A missing check of an inode number with an invalid value of zero can cause an out-of-bounds read and result in a denial of service.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2278338
Bug Blocks:	2278552

Description Zack Miele 2024-05-01 19:27:45 UTC

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

Squashfs: check the inode number is not the invalid value of zero

The Linux kernel CVE team has assigned CVE-2024-26982 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024050141-CVE-2024-26982-8675@gregkh/T

Comment 1 Zack Miele 2024-05-01 19:28:17 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2278338]

Comment 16 errata-xmlrpc 2024-07-02 08:55:30 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:4211 https://access.redhat.com/errata/RHSA-2024:4211

Comment 17 errata-xmlrpc 2024-07-08 02:02:39 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:4352 https://access.redhat.com/errata/RHSA-2024:4352

Comment 18 errata-xmlrpc 2024-07-24 13:12:00 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Extended Update Support

Via RHSA-2024:4823 https://access.redhat.com/errata/RHSA-2024:4823

Comment 19 errata-xmlrpc 2024-07-24 13:24:03 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Extended Update Support

Via RHSA-2024:4831 https://access.redhat.com/errata/RHSA-2024:4831

Comment 20 errata-xmlrpc 2024-07-31 00:40:17 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:4928 https://access.redhat.com/errata/RHSA-2024:4928

Comment 21 errata-xmlrpc 2024-08-13 00:27:03 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Extended Update Support

Via RHSA-2024:5255 https://access.redhat.com/errata/RHSA-2024:5255

Comment 22 errata-xmlrpc 2024-09-04 07:18:59 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service

Via RHSA-2024:6297 https://access.redhat.com/errata/RHSA-2024:6297