In the Linux kernel, the following vulnerability has been resolved: udf: Do not bother merging very long extents When merging very long extents we try to push as much length as possible to the first extent. However this is unnecessarily complicated and not really worth the trouble. Furthermore there was a bug in the logic resulting in corrupting extents in the file as syzbot reproducer shows. So just don't bother with the merging of extents that are too long together.
Update Linux/Linux to d52252a1de4cf96a34f722b0cd8902d8ff78eb57 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanudf: Do not bother merging very long extents affects Linux/Linux (generic), Linux/Linux (generic). Severity is high. In the Linux kernel, the following vulnerability has been resolved: udf: Do not bother merging very long extents When merging very long extents we try to push as much length as possible to the first extent. However this is unnecessarily complicated and not really worth the trouble. Furthermore there was a bug in the logic resulting in corrupting extents in the file as syzbot reproducer shows. So just don't bother with the merging of extents that are too long together.
AI coding agents often install or upgrade packages automatically in generic. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d52252a1de4cf96a34f722b0cd8902d8ff78eb57 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d029799d381a9ee06209a222cae75f04c5d5304 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d20e3b768aff32112bdce8d3219d923ae75f9f1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <965982feb333aefa9256c0fe188b5f1b958aef63 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9a8d602f0723586e668bae7e65c832ceb9bcc8bc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <adac9ac6d2e04ea0782b91a00ba10706002f3ec4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7a965da79f2d22601f329cbfce588386b0847544 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced |
In the Linux kernel, the following vulnerability has been resolved: udf: Do not bother merging very long extents When merging very long extents we try to push as much length as possible to the first extent. However this is unnecessarily complicated and not really worth the trouble. Furthermore there was a bug in the logic resulting in corrupting extents in the file as syzbot reproducer shows. So just don't bother with the merging of extents that are too long together.
Update Linux/Linux to d52252a1de4cf96a34f722b0cd8902d8ff78eb57 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanudf: Do not bother merging very long extents affects Linux/Linux (generic), Linux/Linux (generic). Severity is high. In the Linux kernel, the following vulnerability has been resolved: udf: Do not bother merging very long extents When merging very long extents we try to push as much length as possible to the first extent. However this is unnecessarily complicated and not really worth the trouble. Furthermore there was a bug in the logic resulting in corrupting extents in the file as syzbot reproducer shows. So just don't bother with the merging of extents that are too long together.
AI coding agents often install or upgrade packages automatically in generic. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d52252a1de4cf96a34f722b0cd8902d8ff78eb57 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d029799d381a9ee06209a222cae75f04c5d5304 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d20e3b768aff32112bdce8d3219d923ae75f9f1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <965982feb333aefa9256c0fe188b5f1b958aef63 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9a8d602f0723586e668bae7e65c832ceb9bcc8bc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <adac9ac6d2e04ea0782b91a00ba10706002f3ec4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7a965da79f2d22601f329cbfce588386b0847544 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced |
| d52252a1de4cf96a34f722b0cd8902d8ff78eb57, 5d029799d381a9ee06209a222cae75f04c5d5304, 3d20e3b768aff32112bdce8d3219d923ae75f9f1, 965982feb333aefa9256c0fe188b5f1b958aef63, 9a8d602f0723586e668bae7e65c832ceb9bcc8bc, adac9ac6d2e04ea0782b91a00ba10706002f3ec4, 7a965da79f2d22601f329cbfce588386b0847544, 53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| d52252a1de4cf96a34f722b0cd8902d8ff78eb57, 5d029799d381a9ee06209a222cae75f04c5d5304, 3d20e3b768aff32112bdce8d3219d923ae75f9f1, 965982feb333aefa9256c0fe188b5f1b958aef63, 9a8d602f0723586e668bae7e65c832ceb9bcc8bc, adac9ac6d2e04ea0782b91a00ba10706002f3ec4, 7a965da79f2d22601f329cbfce588386b0847544, 53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard