Bug 2482113 (CVE-2026-45991) - CVE-2026-45991 kernel: udf: fix partition descriptor append bookkeeping
Summary: CVE-2026-45991 kernel: udf: fix partition descriptor append bookkeeping
Keywords:
Status: NEW
Alias: CVE-2026-45991
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-27 15:11 UTC by OSIDB Bzimport
Modified: 2026-08-20 05:22 UTC (History)
2 users (show)

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-2026:54246 0 None None None 2026-08-12 09:06:08 UTC
Red Hat Product Errata RHSA-2026:54247 0 None None None 2026-08-12 08:51:06 UTC
Red Hat Product Errata RHSA-2026:57251 0 None None None 2026-08-20 05:22:19 UTC
Red Hat Product Errata RHSA-2026:57252 0 None None None 2026-08-20 05:13:29 UTC

Description OSIDB Bzimport 2026-05-27 15:11:56 UTC
In the Linux kernel, the following vulnerability has been resolved:

udf: fix partition descriptor append bookkeeping

Mounting a crafted UDF image with repeated partition descriptors can
trigger a heap out-of-bounds write in part_descs_loc[].

handle_partition_descriptor() deduplicates entries by partition number,
but appended slots never record partnum. As a result duplicate
Partition Descriptors are appended repeatedly and num_part_descs keeps
growing.

Once the table is full, the growth path still sizes the allocation from
partnum even though inserts are indexed by num_part_descs. If partnum is
already aligned to PART_DESC_ALLOC_STEP, ALIGN(partnum, step) can keep
the old capacity and the next append writes past the end of the table.

Store partnum in the appended slot and size growth from the next append
count so deduplication and capacity tracking follow the same model.

Comment 4 errata-xmlrpc 2026-08-12 08:51:05 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:54247 https://access.redhat.com/errata/RHSA-2026:54247

Comment 5 errata-xmlrpc 2026-08-12 09:06:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:54246 https://access.redhat.com/errata/RHSA-2026:54246

Comment 6 errata-xmlrpc 2026-08-20 05:13:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:57252 https://access.redhat.com/errata/RHSA-2026:57252

Comment 7 errata-xmlrpc 2026-08-20 05:22:18 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:57251 https://access.redhat.com/errata/RHSA-2026:57251


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