
Pardus 21.5 (amd64) için CVE-2026-98432 düzeltmesini Linux 5.10.262 tabanına taşıyan gayriresmî topluluk yaması. Proje, yamalı kaynak kodu, test edilen .deb paketini ve derleme, kurulum ve geri dönüş adımlarını içerir.
Suggested repository name pardus21-cve-2026-98432. Suggested release tag v5.10.262-mtombak-cve98432-1. Community build prepared by Muhammed Emin Tombak.
This work is an unofficial community build that backports the Linux 5.10 stable fix for CVE-2026-98432 onto the 5.10.262-1 base used on Pardus 21.5 amd64. TCP/IPv4 option memory is held until RCU readers complete. The author of the original fix is Eric Dumazet. The first release in the Linux 5.10 series to include the fix is 5.10.272. Linux 5.10.272 changelog
For Pardus 21.5, release support under Pardus's official schedule ended on 1 May 2025, and Debian LTS support for Debian 11 Bullseye, the distribution's base, ended on 31 August 2026. During the work, no kernel package containing the CVE-2026-98432 fix could be found in the test system's Pardus 21 (yirmibir) APT repositories. For this system, which must remain on the existing 5.10.262 base, we backported the Linux 5.10 stable fix. The scope of this community work is limited to CVE-2026-98432. Pardus release schedule · Debian LTS announcement
linux-source-5.10_5.10.262-1_all.deb. The SHA-256 value of the local copy matched the APT package record.b3b027ef0cd322bfa839b9aaf5b27551eea54cf6. Upstream commit e3f33b0a1d89d738e2b913dab519226eaf76e15b.CVE-2026-98432-5.10.patch was applied to the clean base with zero fuzz. The two relevant IPv4 files matched byte-for-byte with their counterparts in the stored build tree..config has the same SHA-256 value as /boot/config-5.10.262-mtombak-cve98432 in the tested package.make -j2 bindeb-pkg. The build used GCC 10.2.1 and GNU linker 2.35.2. The build log includes dpkg 1.20.14, flex 2.6.4-8, bison 2:3.7.5+dfsg-1, libelf-dev 0.183-1 and libssl-dev 1.1.1w-0+deb11u8. This selection is not the complete list of dependencies.Example of preparing the source tree in a clean working directory, with the verified source package and the patch placed in the same directory:
dpkg-deb -x linux-source-5.10_5.10.262-1_all.deb kaynak-paket
tar -xJf kaynak-paket/usr/src/linux-source-5.10.tar.xz
cd linux-source-5.10
patch --dry-run --forward --fuzz=0 -p1 -i ../CVE-2026-98432-5.10.patch
patch --forward --fuzz=0 -p1 -i ../CVE-2026-98432-5.10.patch
At the root of the source tree, place the configuration from the archive as .config. The build environment must include GCC, GNU binutils, make, dpkg packaging tools, bc, rsync, kmod, cpio, bison, flex, libelf-dev and libssl-dev. The tested command was make -j2 bindeb-pkg. The open-parameter recipe targeting the same package identity is below.
cp ../config/config-5.10.262-mtombak-cve98432 .config
make -j2 ARCH=x86 KBUILD_DEBARCH=amd64 \
KDEB_SOURCENAME=linux-mtombak-cve98432 \
KDEB_PKGVERSION=5.10.262-mtombak-cve98432-1 \
KDEB_CHANGELOG_DIST=yirmibir bindeb-pkg
This open-parameter recipe was not re-run. Inputs such as build time and module signature can affect the binary output. The private signing key of the current package is not included in the release files. The packaging stage produces the debian/ files.
The one-way checksum comparison from the patched clean base to the build tree reported no differences. Additional paths in the build tree were also listed. After filtering, the 150 paths examined are consistent, by their visible names, with configuration, packaging, or generated build files. This classification is based on file names.
This draft does not include the source base itself. Before binary release, release access must be provided for the exactly corresponding source and packaging inputs. Use the locally verified base file together with the archive.
The release candidate is only the linux-image package. In the tested installation, linux-headers and linux-libc-dev were not installed. Check the package hash before installation and keep the running old kernel. For an APT simulation, in the directory containing the file, apt -s install ./linux-image-5.10.262-mtombak-cve98432_5.10.262-mtombak-cve98432-1_amd64.deb can be used. Review the changes in the simulation. On first boot, select the custom kernel from GRUB's advanced options and verify after boot with uname -r. If a rollback is needed, select the previous kernel from the same menu. If a persistent default has been set, the GRUB default must also be corrected for rollback.
| File | SHA-256 |
|---|---|
| Source package | 4f01148344ca9e5c1c9743ab4a084cf61c437548f803443ccc044602278b52bc |
| Patch | 09c3f7008aeb76288752c597c12df0c4d1b8b0760742d21d368861c0f7005646 |
| Final configuration | c7257ba7782a5416c56a513b7d3867dd94f80dd78786679f21a2524b9a84b87d |
| linux-image .deb | b275ee97c5652af225137112a7c10b1e0ffff29dd1ac960f9a1b4d69699d54e3 |
Two boots succeeded on a single Pardus 21.5 amd64 machine. The persistent GRUB selection was verified on the second boot. On the first boot, iSCSI and SMB read/write checks from a Windows client passed. On the second boot, iSCSI reconnection and SMB directory access were verified. Graphics and Ethernet worked. Existing Ethernet disconnections and the EFI FAT warning are open maintenance findings. A fanotify warning was observed while security software was running. Secure Boot was disabled. Dynamic exploit/KASAN testing and compatibility testing on other hardware were not performed. The scope is limited to this CVE.