<?xml version="1.0" encoding="utf-8"?>
<!--RSS generated by Flaimo.com RSS Builder [2026-03-07 14:32:40]-->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><docs>https://bugs.rockylinux.org/</docs><link>https://bugs.rockylinux.org/</link><description><![CDATA[Rocky Linux BugTracker - Issues]]></description><title>Rocky Linux BugTracker - Issues</title><image><title>Rocky Linux BugTracker - Issues</title><url>https://bugs.rockylinux.org/images/mantis_logo.png</url><link>https://bugs.rockylinux.org/</link><description><![CDATA[Rocky Linux BugTracker - Issues]]></description></image><language>en</language><category>All Projects</category><ttl>10</ttl><dc:language>en</dc:language><sy:updatePeriod>hourly</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>0012211: SELinux regression in selinux-policy-42.1.7-1.el10_1.1 causes systemd AVC denial (init_t capability2 mac_admin) and breaks syste</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12211</link><description><![CDATA[After upgrading to selinux-policy-42.1.7-1.el10_1.1 on Rocky Linux 10.1, SELinux starts denying the mac_admin capability for systemd (init_t). This results in repeated AVC denials and causes system services to malfunction. In our environment this manifests as failures when managing services (for example via systemctl or automation tools such as Ansible).&lt;br /&gt;
&lt;br /&gt;
Downgrading SELinux policy packages to 42.1.7-1.el10 resolves the issue immediately.&lt;br /&gt;
&lt;br /&gt;
Working versions:&lt;br /&gt;
&lt;br /&gt;
selinux-policy-42.1.7-1.el10.noarch&lt;br /&gt;
selinux-policy-targeted-42.1.7-1.el10.noarch&lt;br /&gt;
systemd-257-13.el10.rocky.0.1.x86_64&lt;br /&gt;
dbus-broker-36-4.el10.x86_64&lt;br /&gt;
&lt;br /&gt;
Broken versions:&lt;br /&gt;
&lt;br /&gt;
selinux-policy-42.1.7-1.el10_1.1.noarch&lt;br /&gt;
selinux-policy-targeted-42.1.7-1.el10_1.1.noarch]]></description><category>selinux-policy</category><pubDate>Fri, 06 Mar 2026 09:22:06 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12211</guid><comments>https://bugs.rockylinux.org/view.php?id=12211#bugnotes</comments></item><item><title>0012112: Raspberry Pi, Rocky Linux 10 image fails to boot on Pi-4 Model B</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12112</link><description><![CDATA[The image &quot;Rocky-10-SBC-RaspberryPi.latest.aarch64.raw.xz&quot; available as of 21-Feb-2026 as a download from the Rocky Linux website fails to boot on a Raspberry Pi-4 Model B with 8GB RAM when written to a 32GB SD-card.&lt;br /&gt;
&lt;br /&gt;
At boot the Raspberry boot loader display is presented for approx. 500ms, followed by the colourful, rainbow-like, Raspberry splash screen.  Nothing else is ever shown on the display and RL fails to boot.  The Pi motherboard has two LED's.  Red has continuous illumination, the green flashes seven times, pauses momentarily and then repeats the pattern.&lt;br /&gt;
&lt;br /&gt;
The Rocky Linux 10 README for the Raspberry Pi image identifies that it has been tested (and presumably works) with a Pi 4:&lt;br /&gt;
&lt;br /&gt;
&quot;This image is always available at: &lt;a href=&quot;https://dl.rockylinux.org/pub/rocky/10/images/aarch64/Rocky-10-SBC-RaspberryPi.latest.aarch64.raw.xz&quot; rel=&quot;noopener&quot;&gt;https://dl.rockylinux.org/pub/rocky/10/images/aarch64/Rocky-10-SBC-RaspberryPi.latest.aarch64.raw.xz&lt;/a&gt;&lt;br /&gt;
They have been tested on Raspberry Pi 4 and 5.&lt;br /&gt;
Rocky Linux 10 WILL NOT WORK on a Raspberry Pi 1 or 2 (1.1 or earlier) as they are 32-bit only, and Rocky Linux only supports arm64 (aarch64).&lt;br /&gt;
Rocky Linux 10 WILL NOT WORK on a Raspberry Pi 3 due to lack of MBR on the images.&quot;]]></description><category>General</category><pubDate>Wed, 04 Mar 2026 08:33:19 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12112</guid><comments>https://bugs.rockylinux.org/view.php?id=12112#bugnotes</comments></item><item><title>0012180: Trusted Domain Authentication samba 4.22 Rocky 9.7</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12180</link><description><![CDATA[Samba 4.22.4-12.el9_7 doesn't seem to contain the regression anymore for CVE-2025-49716 netlogon hardening fix&lt;br /&gt;
&lt;br /&gt;
- **OS**: Rocky Linux 9.7 (Blue Onyx)&lt;br /&gt;
- **Samba Version**: samba-4.22.4-12.el9_7.x86_64&lt;br /&gt;
- **Configuration**: Domain member server joined to DOMAIN-A.COM with forest transitive trust to DOMAIN-B.COM&lt;br /&gt;
- **idmap backend**: ad (for DOMAIN-B), sss (for DOMAIN-A)&lt;br /&gt;
&lt;br /&gt;
After upgrading from Rocky Linux 9.6 (samba-4.21.3-14.el9_6) to Rocky Linux 9.7 (samba-4.22.4-12.el9_7), NTLM challenge/response authentication fails for users from the trusted domain DOMAIN-B.COM with `NT_STATUS_WRONG_PASSWORD`. Plaintext authentication works correctly.&lt;br /&gt;
&lt;br /&gt;
[log.wb-DOMAIN-B] cm_connect_netlogon_transport: get_secure_channel_type gave SEC_CHAN_NULL for DOMAIN-B&lt;br /&gt;
[log.wb-DOMAIN-B] cli_rpc_pipe_open_noauth: opened pipe netlogon to machine DC01.domain-b.com and bound anonymously&lt;br /&gt;
[log.winbindd] lm_resp: DATA_BLOB length=0&lt;br /&gt;
[log.winbindd] nt_resp: DATA_BLOB length=0&lt;br /&gt;
[log.winbindd] result: NT_STATUS_WRONG_PASSWORD&lt;br /&gt;
&lt;br /&gt;
No `netr_LogonSamLogon` calls found in logs - winbind not attempting netlogon authentication for trusted domain challenge/response.]]></description><category>samba</category><pubDate>Tue, 03 Mar 2026 18:30:50 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12180</guid><comments>https://bugs.rockylinux.org/view.php?id=12180#bugnotes</comments></item><item><title>0012179: Security update for CVE-2025-14104 missing for Rocky 9.7 util-linux package</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12179</link><description><![CDATA[The security updates for CVE-2025-14104 were provided as following:&lt;br /&gt;
&lt;br /&gt;
- el8: [util-linux-0:2.32.1-48.el8_10] via RHSA-2026:1852 (2026-02-04)  &lt;-- This was made available on 2026-02-05&lt;br /&gt;
- el9: [util-linux-0:2.37.4-21.el9_7] via RHSA-2026:1913 (2026-02-04)   &lt;-- Still missing (not the same as util-linux-0:2.37.4-21.el9)&lt;br /&gt;
&lt;br /&gt;
The &lt;a href=&quot;https://errata.rockylinux.org/RLSA-2026:1913&quot; rel=&quot;noopener&quot;&gt;https://errata.rockylinux.org/RLSA-2026:1913&lt;/a&gt; does not appear to denote the correct version for this security update. It references util-linux-0:2.37.4-21.el9 (which was released 2025-05-03 and does not contain the security fix in question (refer to additional information for first 10 lines of changelogs).&lt;br /&gt;
&lt;br /&gt;
Can this security update be made available for the Rocky el9.7 release?]]></description><category>util-linux</category><pubDate>Tue, 03 Mar 2026 16:23:31 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12179</guid><comments>https://bugs.rockylinux.org/view.php?id=12179#bugnotes</comments></item><item><title>0012178: [Account Services] Data hash table of rotation spam in DMESG</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12178</link><description><![CDATA[Please update this package as sometimes it is nearly impossible find info directly in the dmesg&lt;br /&gt;
please refer to &lt;br /&gt;
&lt;a href=&quot;https://github.com/systemd/systemd/commit/afc47ee2af456d12670df862457dcc7f6b864d79&quot; rel=&quot;noopener&quot;&gt;https://github.com/systemd/systemd/commit/afc47ee2af456d12670df862457dcc7f6b864d79&lt;/a&gt;]]></description><category>BugTracker</category><pubDate>Tue, 03 Mar 2026 14:29:43 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12178</guid><comments>https://bugs.rockylinux.org/view.php?id=12178#bugnotes</comments></item><item><title>0011287: cannot update to 9.7 from 9.6</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11287</link><description><![CDATA[I am trying to update from 9.6 to 9.7 and hitting an error which I want to run by you to see if you know it and what the best solution is. I don't understand enough to be able to know where your &quot;try to add&quot; suggestions of --allowerasing, --skip-broken, and/or --nobest is appropriate]]></description><category>General</category><pubDate>Mon, 02 Mar 2026 01:08:26 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11287</guid><comments>https://bugs.rockylinux.org/view.php?id=11287#bugnotes</comments></item><item><title>0012079: 10.x devel repository mirrors not working</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12079</link><description><![CDATA[Enabling the &quot;Devel&quot; repository for 10.0 and 10.x fails. It stopped working sometime in the last couple of months or so.&lt;br /&gt;
&lt;br /&gt;
A similar bug was previously reported for 9.x: &lt;a href=&quot;https://bugs.rockylinux.org/view.php?id=3268&quot; rel=&quot;noopener&quot;&gt;https://bugs.rockylinux.org/view.php?id=3268&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Note that this is in the context of building a custom Docker image within a GitHub Actions workflow, based on rockylinux/rockylinux from Docker Hub.]]></description><category>Mirror Manager</category><pubDate>Thu, 26 Feb 2026 06:57:05 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12079</guid><comments>https://bugs.rockylinux.org/view.php?id=12079#bugnotes</comments></item><item><title>0012046: Rocky Linux Boot gives text full of squares on the console ( screen ) after the kernel update to Latest ( 4.18.0-553.104.1 )</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12046</link><description><![CDATA[We updated the kernel version from kernel-4.18.0-553.97.1.el8_10 to kernel-4.18.0-553.104.1.el8_10.&lt;br /&gt;
&lt;br /&gt;
Then, Booting the rocky server gives white squares full on screen for few seconds.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please let us know , if this issue is known or tracked , if tracked please give more details on it .&lt;br /&gt;
&lt;br /&gt;
Thanks.]]></description><category>kernel</category><pubDate>Sat, 21 Feb 2026 18:26:29 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12046</guid><comments>https://bugs.rockylinux.org/view.php?id=12046#bugnotes</comments></item><item><title>0012013: CVE-2025-7425 missing from Rocky8 errata</title><author></author><link>https://bugs.rockylinux.org/view.php?id=12013</link><description><![CDATA[Was fixed some time ago in Redhat 8: &lt;a href=&quot;https://access.redhat.com/security/cve/cve-2025-7425&quot; rel=&quot;noopener&quot;&gt;https://access.redhat.com/security/cve/cve-2025-7425&lt;/a&gt; (August 2025)&lt;br /&gt;
Rocky 9 has picked up the fix: &lt;a href=&quot;https://errata.rockylinux.org/RLSA-2025:12447&quot; rel=&quot;noopener&quot;&gt;https://errata.rockylinux.org/RLSA-2025:12447&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Current builds show #12 27.72  libxml2                    x86_64 2.9.7-21.el8_10.3            baseos    697 k]]></description><category>libxml2</category><pubDate>Mon, 16 Feb 2026 05:05:47 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=12013</guid><comments>https://bugs.rockylinux.org/view.php?id=12013#bugnotes</comments></item><item><title>0011980: On Rocky Linux 9, perl-DBD-MySQL-4.053-1.el9.0.1.x86_64 has a hard runtime dependency on libmysqlclient.so.21</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11980</link><description><![CDATA[On Rocky Linux 9, perl-DBD-MySQL-4.053-1.el9.0.1.x86_64 has a hard runtime dependency on libmysqlclient.so.21 -&lt;br /&gt;
This makes perl-DBD-MySQL incompatible with Percona Server packages - (percona-server-shared) which obsolete mysql-libs.&lt;br /&gt;
&lt;br /&gt;
On RHEL 9, perl-DBD-MySQL is available in a build (4.050-13.el9) which uses mariadb-connector-c and does not require libmysqlclient.so.21, and therefore works correctly with Percona Server.&lt;br /&gt;
&lt;br /&gt;
As a result, percona-xtrabackup-84 cannot be installed on Rocky 9 when Percona Server is present, while the same setup works on RHEL 9.&lt;br /&gt;
&lt;br /&gt;
Please consider rebuilding perl-DBD-MySQL on Rocky 9 against mariadb-connector-c (as in RHEL), or providing a compatible build as this differs from RHEL spec / behavior.]]></description><category>perl-DBD-MySQL</category><pubDate>Sat, 07 Feb 2026 20:14:07 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11980</guid><comments>https://bugs.rockylinux.org/view.php?id=11980#bugnotes</comments></item><item><title>0011947: AWS &amp; GCP NIC PMDs missing from RPM on ARM</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11947</link><description><![CDATA[On AWS the c7gn and c8gn are the most cost effective instance types to use with DPDK as a virtual network appliance and both use Graviton ARM cores. The current DPDK RPM only enables the ENA driver on x86-64 and not on ARM. Same issue with the GCP gve driver.]]></description><category>dpdk</category><pubDate>Tue, 03 Feb 2026 09:01:08 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11947</guid><comments>https://bugs.rockylinux.org/view.php?id=11947#bugnotes</comments></item><item><title>0011914: WSL Image Cannot Execute Windows Binaries By Default</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11914</link><description><![CDATA[After installing the Rocky 10 WSL image it cannot execute Windows binaries by default. Trying to do so will fail with the following error:&lt;br /&gt;
&lt;br /&gt;
[&lt;a href=&quot;mailto:user@host&quot;&gt;user@host&lt;/a&gt; ~]$ ssh.exe&lt;br /&gt;
-bash: /mnt/c/WINDOWS/System32/OpenSSH/ssh.exe: cannot execute binary file: Exec format error&lt;br /&gt;
&lt;br /&gt;
This is a known issue when systemd is enabled in a WSL issue and there is a resolution as seen here: &lt;a href=&quot;https://serverfault.com/a/1141563&quot; rel=&quot;noopener&quot;&gt;https://serverfault.com/a/1141563&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
sudo sh -c 'echo :WSLInterop:M::MZ::/init:PF &gt; /usr/lib/binfmt.d/WSLInterop.conf'&lt;br /&gt;
sudo systemctl restart systemd-binfmt&lt;br /&gt;
&lt;br /&gt;
Given the WSL image enables systemd by default, it would be good to include the above file in the image. Failing that, it would be good to mention this in the documentation at &lt;a href=&quot;https://docs.rockylinux.org/10/guides/interoperability/import_rocky_to_wsl/&quot; rel=&quot;noopener&quot;&gt;https://docs.rockylinux.org/10/guides/interoperability/import_rocky_to_wsl/&lt;/a&gt;]]></description><category>General</category><pubDate>Wed, 28 Jan 2026 20:22:30 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11914</guid><comments>https://bugs.rockylinux.org/view.php?id=11914#bugnotes</comments></item><item><title>0011881: The AWS marketplace AMIs of Rocky Linux 9 with LVM (Official) is outdated</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11881</link><description><![CDATA[Please update the AWS Marketplace offering of Rocky Linux 9 with LVM (Official) to current release 9.7. (&lt;a href=&quot;https://rockylinux.org/news/rocky-linux-9-7-ga-release&quot; rel=&quot;noopener&quot;&gt;https://rockylinux.org/news/rocky-linux-9-7-ga-release&lt;/a&gt;)]]></description><category>General</category><pubDate>Tue, 27 Jan 2026 07:34:10 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11881</guid><comments>https://bugs.rockylinux.org/view.php?id=11881#bugnotes</comments></item><item><title>0011848: The AWS marketplace AMIs of Rocky 9 and 10 lack support for p4de instances while p4d instances are supported</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11848</link><description><![CDATA[Please add support for AWS EC2 p4de instances in AWS Marketplace. p4d instances are already supported, but p4de offers more GPU memory (80GB per GPU) which is required for some ML applications.]]></description><category>General</category><pubDate>Mon, 26 Jan 2026 10:40:22 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11848</guid><comments>https://bugs.rockylinux.org/view.php?id=11848#bugnotes</comments></item><item><title>0011815: kernel-debuginfo-rpm for initial Rocky Linux 9.4 kernel (5.14.0-427.13.1) missing from official rocky repository</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11815</link><description><![CDATA[Hi:&lt;br /&gt;
The initial release of Rocky Linux 9.4 ships with the following kernel version:5.14.0-427.13.1.el9_4.x86_64&lt;br /&gt;
However, the corresponding kernel-debuginfo RPM for this exact kernel version is missing from the official Rocky Linux repository. I checked the official Rocky Linux 9.4 vault repository:&lt;a href=&quot;https://dl.rockylinux.org/vault/rocky/9.4/BaseOS/x86_64/debug/tree/Packages/k/,&quot; rel=&quot;noopener&quot;&gt;https://dl.rockylinux.org/vault/rocky/9.4/BaseOS/x86_64/debug/tree/Packages/k/,&lt;/a&gt; In this directory, the lowest available kernel-debuginfo RPM version is: kernel-debuginfo-5.14.0-427.16.1.el9_4.x86_64.rpm.  Because the debuginfo RPM matching the initial 9.4 kernel is missing, it is not possible to analyze vmcore files using the crash utility and vmlinux on systems running:&lt;br /&gt;
&lt;br /&gt;
For comparison:&lt;br /&gt;
- Rocky Linux 9.3 provides kernel-debuginfo RPMs for its initial kernel release&lt;br /&gt;
- Rocky Linux 9.5 also provides kernel-debuginfo RPMs for its initial kernel release&lt;br /&gt;
Only Rocky Linux 9.4 appears to be missing the kernel-debuginfo RPM for its first released kernel version.&lt;br /&gt;
&lt;br /&gt;
Please upload kernel-debuginfo-5.14.0-427.13.1.el9_4.x86_64. RPM in the official Rocky Linux repository&lt;br /&gt;
&lt;br /&gt;
Thank you for your help.]]></description><category>kernel</category><pubDate>Thu, 22 Jan 2026 20:49:57 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11815</guid><comments>https://bugs.rockylinux.org/view.php?id=11815#bugnotes</comments></item><item><title>0011782: liboath 2.6.12-1 doesn't work if usersfile contains $HOME or $USER</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11782</link><description><![CDATA[Dear Maintainer,&lt;br /&gt;
&lt;br /&gt;
Due to CVE-2024-47191 liboath now drops privileges if the OTP token (the &quot;usersfile&quot; given in the pam configuration) is set to a path containing &quot;$HOME&quot; or &quot;$USER&quot;.&lt;br /&gt;
&lt;br /&gt;
The default lockfile location is &quot;/var/lock/pam_oath.lock&quot;, which is writable only by root. On an OTP check, the process is to drop privileges, then ask for OTP, and if the OTP is okay to modify the &quot;usersfile&quot; (by creatting first an exclusive lock).&lt;br /&gt;
&lt;br /&gt;
If the lock can&quot;t be created, OTP fails.&lt;br /&gt;
&lt;br /&gt;
I can specify a lockfile manually, but I can't use &quot;$HOME&quot; or &quot;$USER&quot; so each user's lockfile is independent from one user to another.]]></description><category>liboauth</category><pubDate>Tue, 20 Jan 2026 10:41:53 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11782</guid><comments>https://bugs.rockylinux.org/view.php?id=11782#bugnotes</comments></item><item><title>0011749: On Rocky Linux 10.1, the postfix package (postfix-3.8.5-8.el10.x86_64) was built against OpenSSL 3.2.x headers</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11749</link><description><![CDATA[### Summary&lt;br /&gt;
On Rocky Linux 10.1, the postfix package (postfix-3.8.5-8.el10.x86_64) was built against OpenSSL 3.2.x headers but at runtime uses OpenSSL 3.5.1, causing:&lt;br /&gt;
&lt;br /&gt;
warning: run-time library vs. compile-time header version mismatch: OpenSSL 3.5.1 may not be compatible with OpenSSL 3.2.0&lt;br /&gt;
&lt;br /&gt;
This warning appears each time SMTP/TLS is negotiated in Postfix logs.]]></description><category>postfix</category><pubDate>Sun, 18 Jan 2026 16:20:47 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11749</guid><comments>https://bugs.rockylinux.org/view.php?id=11749#bugnotes</comments></item><item><title>0011716: System enters a boot loop when a systemd service uses StandardError=journal+console and writes to stderr.</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11716</link><description><![CDATA[If a systemd service file contains StandardError=journal+console and something is written to stderr, the system enters a boot loop. Occasionally, the system starts normally.&lt;br /&gt;
If the service file contains only StandardError=journal, the system starts normally.&lt;br /&gt;
I selected the “Kernel” category because this issue occurs only with the following kernel versions:&lt;br /&gt;
&lt;br /&gt;
5.14.0-611.16.1.el9_7.x86_64&lt;br /&gt;
5.14.0-611.11.1.el9_7.x86_64&lt;br /&gt;
&lt;br /&gt;
With kernel 5.14.0-570.52.1.el9_6.x86_64, everything works as expected.&lt;br /&gt;
&lt;br /&gt;
I did not find anything useful in the log files, but &quot;ipmitool sel list&quot; shows the following output:&lt;br /&gt;
&lt;br /&gt;
  4c | 01/13/2026 | 13:40:17 | Processor #0x97 | IERR | Asserted&lt;br /&gt;
  4d | 01/13/2026 | 13:40:17 | Critical Interrupt | Bus Uncorrectable error | Asserted&lt;br /&gt;
  4e | 01/13/2026 | 13:40:17 | Processor | Configuration Error | Asserted&lt;br /&gt;
&lt;br /&gt;
System:&lt;br /&gt;
&lt;br /&gt;
Processor:&lt;br /&gt;
processor       : 0&lt;br /&gt;
vendor_id       : GenuineIntel&lt;br /&gt;
cpu family      : 6&lt;br /&gt;
model           : 143&lt;br /&gt;
model name      : Intel(R) Xeon(R) Gold 5412U&lt;br /&gt;
stepping        : 8&lt;br /&gt;
microcode       : 0x2b000643&lt;br /&gt;
cpu MHz         : 800.000&lt;br /&gt;
cache size      : 46080 KB&lt;br /&gt;
physical id     : 0&lt;br /&gt;
siblings        : 48&lt;br /&gt;
core id         : 0&lt;br /&gt;
cpu cores       : 24&lt;br /&gt;
apicid          : 0&lt;br /&gt;
initial apicid  : 0&lt;br /&gt;
fpu             : yes&lt;br /&gt;
fpu_exception   : yes&lt;br /&gt;
cpuid level     : 32&lt;br /&gt;
wp              : yes&lt;br /&gt;
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 intel_ppin cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect user_shstk avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req vnmi avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr ibt amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities&lt;br /&gt;
vmx flags       : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb ept_5level flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs pml ept_violation_ve ept_mode_based_exec tsc_scaling usr_wait_pause notify_vm_exiting ipi_virt&lt;br /&gt;
bugs            : spectre_v1 spectre_v2 spec_store_bypass swapgs eibrs_pbrsb bhi spectre_v2_user vmscape&lt;br /&gt;
bogomips        : 4200.00&lt;br /&gt;
clflush size    : 64&lt;br /&gt;
cache_alignment : 64&lt;br /&gt;
address sizes   : 52 bits physical, 57 bits virtual&lt;br /&gt;
power management:]]></description><category>kernel</category><pubDate>Tue, 13 Jan 2026 16:05:15 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11716</guid><comments>https://bugs.rockylinux.org/view.php?id=11716#bugnotes</comments></item><item><title>0011683: OS crash issue</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11683</link><description><![CDATA[The system experiences multiple crashes, with VMCORE logs recorded.&lt;br /&gt;
RIP: 0010:__mmu_notifier_arch_invalidate_secondary_tlbs+0x2c/0x80&lt;br /&gt;
&lt;br /&gt;
[    8.765045] AMD64 EDAC driver v3.5.0&lt;br /&gt;
[    8.771340] intel_rapl_common: Found RAPL domain package&lt;br /&gt;
[    8.771345] intel_rapl_common: Found RAPL domain core&lt;br /&gt;
[    8.772886] intel_rapl_common: Found RAPL domain package&lt;br /&gt;
[    8.772891] intel_rapl_common: Found RAPL domain core&lt;br /&gt;
[    8.773102] AMD Address Translation Library initialized&lt;br /&gt;
[    9.115443] EXT4-fs (nvme0n1): 30 orphan inodes deleted&lt;br /&gt;
[    9.115450] EXT4-fs (nvme0n1): recovery complete&lt;br /&gt;
[    9.117255] EXT4-fs (nvme0n1): mounted filesystem 0eea9178-8b7f-4f5e-9ad5-f399b74e275b r/w with ordered data mode. Quota mode: none.&lt;br /&gt;
[    9.746179] mlx5_core 0000:41:00.0 eth0: renamed from enp65s0f0np0&lt;br /&gt;
[   10.022264] Process accounting resumed&lt;br /&gt;
[   10.840137] mlx5_core 0000:41:00.1 enp65s0f1np1: Link down&lt;br /&gt;
[   11.403156] mlx5_core 0000:41:00.0 eth0: Link up&lt;br /&gt;
[   11.737393] overlayfs: idmapped layers are currently not supported&lt;br /&gt;
[   16.522600] mlx5_core 0000:41:00.1: mlx5_query_module_id:315:(pid 4852): query_mcia_reg failed: status: 0x3&lt;br /&gt;
[   17.325568] Warning: Unmaintained driver is detected: nft_compat&lt;br /&gt;
[   17.476105] block dm-0: the capability attribute has been deprecated.&lt;br /&gt;
[   19.584361] systemd-journald[2533]: Time jumped backwards, rotating.&lt;br /&gt;
[   23.960483] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.&lt;br /&gt;
[   23.960487] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld &lt;&lt;a href=&quot;mailto:Jason@zx2c4.com&quot;&gt;Jason@zx2c4.com&lt;/a&gt;&gt;. All Rights Reserved.&lt;br /&gt;
[   23.960488] TECH PREVIEW: WireGuard may not be fully supported.&lt;br /&gt;
Please review provided documentation for limitations.&lt;br /&gt;
[   25.601606] Warning: Unmaintained driver is detected: ip_set&lt;br /&gt;
[   96.515359] mlx5_core 0000:41:00.1: mlx5_query_mcia:399:(pid 29217): query_mcia_reg failed: status: 0x3&lt;br /&gt;
[   96.515686] mlx5_core 0000:41:00.1 enp65s0f1np1: mlx5e_get_module_eeprom_by_page: mlx5_query_module_eeprom_by_page failed:0xfffffffb&lt;br /&gt;
[   96.516191] mlx5_core 0000:41:00.1: mlx5_query_mcia:399:(pid 29217): query_mcia_reg failed: status: 0x3&lt;br /&gt;
[   96.516484] mlx5_core 0000:41:00.1 enp65s0f1np1: mlx5e_get_module_eeprom_by_page: mlx5_query_module_eeprom_by_page failed:0xfffffffb&lt;br /&gt;
[  202.217367] BUG: unable to handle page fault for address: ffffd880fecc0000&lt;br /&gt;
[  202.217578] #PF: supervisor write access in kernel mode&lt;br /&gt;
[  202.217730] #PF: error_code(0x0002) - not-present page&lt;br /&gt;
[  202.217897] PGD 10003e067 P4D 10003e067 PUD 0 &lt;br /&gt;
[  202.218028] Oops: 0002 [#1] PREEMPT SMP NOPTI&lt;br /&gt;
[  202.218155] CPU: 107 PID: 37544 Comm: python Kdump: loaded Tainted: G               X  -------  ---  5.14.0-427.42.1.el9_4.x86_64 #1&lt;br /&gt;
[  202.218504] Hardware name: Dell Inc. PowerEdge R7525/0W2KKX, BIOS 2.21.1 09/24/2025&lt;br /&gt;
[  202.218728] RIP: 0010:__memcg_kmem_charge_page+0x191/0x270&lt;br /&gt;
[  202.218891] Code: 15 00 00 e9 c1 fe ff ff 65 48 8b 04 25 80 26 03 00 48 8b b8 30 15 00 00 e9 03 ff ff ff e8 27 26 da ff 48 8b 43 10 a8 03 75 36 &lt;65&gt; 48 ff 00 e8 06 6f da ff e9 3e ff ff ff e8 0c 26 da ff 48 8b 43&lt;br /&gt;
[  202.219442] RSP: 0000:ffffb9818731fce0 EFLAGS: 00010246&lt;br /&gt;
[  202.219596] RAX: 00003b1f00000000 RBX: ffff9da62374f000 RCX: 0000000000000000&lt;br /&gt;
[  202.219809] RDX: ffff9ca5d28c1d00 RSI: 0000000000400dc0 RDI: ffff9ca5d28c1d00&lt;br /&gt;
[  202.220024] RBP: 0000000000400dc0 R08: ffff9d61fecf9dd8 R09: 0000000000000000&lt;br /&gt;
[  202.220234] R10: ffff9d61fecf9dc0 R11: 0000000000000018 R12: ffffde0d2c6c9b80&lt;br /&gt;
[  202.220443] R13: ffffde0d2c6c9b80 R14: ffff9da48e3757c0 R15: 0000000000000001&lt;br /&gt;
[  202.220654] FS:  00007fbf17fff640(0000) GS:ffff9d61fecc0000(0000) knlGS:0000000000000000&lt;br /&gt;
[  202.220893] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033&lt;br /&gt;
[  202.221061] CR2: ffffd880fecc0000 CR3: 0000000d9d2b4002 CR4: 0000000000770ee0&lt;br /&gt;
[  202.221269] PKRU: 55555554&lt;br /&gt;
[  202.221349] Call Trace:&lt;br /&gt;
[  202.221423]  &lt;TASK&gt;&lt;br /&gt;
[  202.221484]  ? show_trace_log_lvl+0x1c4/0x2df&lt;br /&gt;
[  202.221615]  ? show_trace_log_lvl+0x1c4/0x2df&lt;br /&gt;
[  202.221744]  ? __alloc_pages+0x11a/0x250&lt;br /&gt;
[  202.221861]  ? __die_body.cold+0x8/0xd&lt;br /&gt;
[  202.221974]  ? page_fault_oops+0x134/0x170&lt;br /&gt;
[  202.222097]  ? kernelmode_fixup_or_oops+0x84/0x110&lt;br /&gt;
[  202.222244]  ? exc_page_fault+0xa8/0x150&lt;br /&gt;
[  202.222374]  ? asm_exc_page_fault+0x22/0x30&lt;br /&gt;
[  202.222506]  ? __memcg_kmem_charge_page+0x191/0x270&lt;br /&gt;
[  202.222649]  __alloc_pages+0x11a/0x250&lt;br /&gt;
[  202.222760]  pte_alloc_one+0x15/0x60&lt;br /&gt;
[  202.222865]  __do_huge_pmd_anonymous_page+0xc6/0x500&lt;br /&gt;
[  202.223014]  __handle_mm_fault+0x661/0x670&lt;br /&gt;
[  202.230385]  ? nohz_balancer_kick+0x1f2/0x250&lt;br /&gt;
[  202.237798]  handle_mm_fault+0xcd/0x290&lt;br /&gt;
[  202.245140]  do_user_addr_fault+0x1b4/0x6a0&lt;br /&gt;
[  202.252516]  ? sched_clock_cpu+0x9/0xc0&lt;br /&gt;
[  202.259775]  exc_page_fault+0x62/0x150&lt;br /&gt;
[  202.266864]  asm_exc_page_fault+0x22/0x30&lt;br /&gt;
[  202.273801] RIP: 0033:0x7fc02c5aa330&lt;br /&gt;
[  202.280932] Code: c1 e8 03 42 0f b6 04 00 d3 f8 83 e0 01 48 8b 4f 10 0f 28 c1 84 c0 74 0a 4a 8d 04 3a f3 42 0f 10 04 a0 49 83 c4 01 49 83 c5 04 &lt;f3&gt; 41 0f 11 45 fc 49 39 cc 7d 45 49 8b 46 18 48 85 c0 75 b4 48 8b&lt;br /&gt;
[  202.295178] RSP: 002b:00007fbf17ffead0 EFLAGS: 00010202&lt;br /&gt;
[  202.301995] RAX: 00007fbb6c00d340 RBX: 0000000000000000 RCX: 00000000010d02cf&lt;br /&gt;
[  202.308825] RDX: 00007fbb6c00d340 RSI: 00007fb4df7555d0 RDI: 0000563048a11030&lt;br /&gt;
[  202.315357] RBP: 00007fbf17ffeb10 R08: 00007fbf3025b660 R09: 0000000000000000&lt;br /&gt;
[  202.321952] R10: 000000000000000a R11: c501b175607c8479 R12: 000000000042aa8d&lt;br /&gt;
[  202.328551] R13: 00007fb4e0800004 R14: 0000563049b29690 R15: 0000000000000000&lt;br /&gt;
[  202.335102]  &lt;/TASK&gt;&lt;br /&gt;
[  202.341644] Modules linked in: xt_CT xt_multiport ipt_rpfilter ip_set_hash_ip ip_set_hash_net ip_set veth wireguard(X) ip6_udp_tunnel udp_tunnel curve25519_x86_64 libcurve25519_generic binfmt_misc nf_conntrack_netlink xt_addrtype xt_statistic xt_nat xt_MASQUERADE xt_mark ipt_REJECT nf_reject_ipv4 nft_chain_nat nf_nat dummy xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_comment nft_compat nft_counter nf_tables libcrc32c nfnetlink overlay dell_rbu amd_atl intel_rapl_msr intel_rapl_common dell_wmi amd64_edac edac_mce_amd ledtrig_audio sparse_keymap rfkill video vfat kvm_amd ipmi_ssif mlx5_ib fat dcdbas kvm ib_uverbs i2c_algo_bit dell_smbios irqbypass drm_shmem_helper dell_wmi_descriptor rapl wmi_bmof drm_kms_helper pcspkr ib_core acpi_ipmi syscopyarea sysfillrect sysimgblt fb_sys_fops ipmi_si ptdma i2c_piix4 k10temp ipmi_devintf ipmi_msghandler acpi_power_meter br_netfilter bridge stp llc fuse drm auth_rpcgss sunrpc ext4 mbcache jbd2 sd_mod sg mlx5_core mlxfw ahci nvme&lt;br /&gt;
[  202.341702]  crct10dif_pclmul libahci psample crc32_pclmul nvme_core crc32c_intel libata tg3 tls ghash_clmulni_intel nvme_common ccp t10_pi pci_hyperv_intf sp5100_tco wmi dm_mirror dm_region_hash dm_log dm_mod&lt;br /&gt;
[  202.414594] CR2: ffffd880fecc0000]]></description><category>crash</category><pubDate>Tue, 13 Jan 2026 04:12:29 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11683</guid><comments>https://bugs.rockylinux.org/view.php?id=11683#bugnotes</comments></item><item><title>0011650: system crashes when copying files from USB stick formated as exFAT</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11650</link><description><![CDATA[system crashes and reboots when copying files from USB stick formated as exFAT to home directory]]></description><category>file</category><pubDate>Thu, 08 Jan 2026 12:07:05 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11650</guid><comments>https://bugs.rockylinux.org/view.php?id=11650#bugnotes</comments></item><item><title>0011617: grep terminates with "Terminated" on Rocky Linux 9</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11617</link><description><![CDATA[Description: When using the grep command on certain system log files (particularly /var/log/messages), the command unexpectedly terminates with the message &quot;Terminated&quot; before completing its operation. This occurs consistently regardless of the search pattern.]]></description><category>General</category><pubDate>Wed, 07 Jan 2026 15:12:08 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11617</guid><comments>https://bugs.rockylinux.org/view.php?id=11617#bugnotes</comments></item><item><title>0011584: Ghostscript 9.27-17.el8_10 horribly outdated and multiple CVE Vulnerabilities</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11584</link><description><![CDATA[GhostScript needs to be upgraded to version 10.05.0 or above.&lt;br /&gt;
&lt;br /&gt;
All NVD Base Score 9.8&lt;br /&gt;
&lt;br /&gt;
CVE-2025-27837&lt;br /&gt;
CVE-2025-27831&lt;br /&gt;
CVE-2025-27836&lt;br /&gt;
CVE-2025-27837&lt;br /&gt;
CVE-2025-27831&lt;br /&gt;
CVE-2025-27836]]></description><category>ghostscript</category><pubDate>Sat, 03 Jan 2026 00:17:16 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11584</guid><comments>https://bugs.rockylinux.org/view.php?id=11584#bugnotes</comments></item><item><title>0011551: Postfix parameter defaults using unsupported map types</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11551</link><description><![CDATA[A couple Postfix parameter defaults use unsupported btree/hash map types:&lt;br /&gt;
&lt;br /&gt;
[&lt;a href=&quot;mailto:root@rocky10&quot;&gt;root@rocky10&lt;/a&gt; ~]# postconf -d | grep btree&lt;br /&gt;
address_verify_map = btree:$data_directory/verify_cache&lt;br /&gt;
postscreen_cache_map = btree:$data_directory/postscreen_cache&lt;br /&gt;
&lt;br /&gt;
[&lt;a href=&quot;mailto:root@rocky10&quot;&gt;root@rocky10&lt;/a&gt; ~]# postconf -d | grep hash&lt;br /&gt;
alias_database = hash:/etc/aliases&lt;br /&gt;
alias_maps = hash:/etc/aliases&lt;br /&gt;
default_database_type = hash&lt;br /&gt;
&lt;br /&gt;
[&lt;a href=&quot;mailto:root@rocky10&quot;&gt;root@rocky10&lt;/a&gt; ~]# postconf -m&lt;br /&gt;
cdb&lt;br /&gt;
cidr&lt;br /&gt;
environ&lt;br /&gt;
fail&lt;br /&gt;
inline&lt;br /&gt;
internal&lt;br /&gt;
ldap&lt;br /&gt;
lmdb&lt;br /&gt;
memcache&lt;br /&gt;
mysql&lt;br /&gt;
pcre&lt;br /&gt;
pgsql&lt;br /&gt;
pipemap&lt;br /&gt;
proxy&lt;br /&gt;
randmap&lt;br /&gt;
regexp&lt;br /&gt;
socketmap&lt;br /&gt;
sqlite&lt;br /&gt;
static&lt;br /&gt;
tcp&lt;br /&gt;
texthash&lt;br /&gt;
unionmap&lt;br /&gt;
unix&lt;br /&gt;
&lt;br /&gt;
Reference: &lt;a href=&quot;https://www.mail-archive.com/postfix-users@postfix.org/msg107023.html&quot; rel=&quot;noopener&quot;&gt;https://www.mail-archive.com/postfix-users@postfix.org/msg107023.html&lt;/a&gt;]]></description><category>postfix</category><pubDate>Mon, 29 Dec 2025 13:55:37 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11551</guid><comments>https://bugs.rockylinux.org/view.php?id=11551#bugnotes</comments></item><item><title>0011518: libsss_idp.so missing from package sssd-idp</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11518</link><description><![CDATA[This seems likely to be a tag along of rocky 9, the package sssd-idp is included in both variants but is only in 9 to supply the `oidc_client` package as a dependency, in 10 however its supposed to both supply that helper and an sssd module for enabling entra and keycloak based authentication to the underlying system. This is done via the file /usr/lib64/sssd/libsss_idp.so.  You'll find this include for example on the package version from fedora 43+.&lt;br /&gt;
&lt;br /&gt;
On os variants before rhel 10 / fedora 43 this module build is skipped with the line: &lt;a href=&quot;https://github.com/SSSD/sssd/blob/87e72fd01387b67e2b9b2aecdae32abe3cfe781f/contrib/sssd.spec.in#L5&quot; rel=&quot;noopener&quot;&gt;https://github.com/SSSD/sssd/blob/87e72fd01387b67e2b9b2aecdae32abe3cfe781f/contrib/sssd.spec.in#L5&lt;/a&gt; but this appears to be getting enforced for rocky 10.1 as well when it shouldn't be.]]></description><category>sssd</category><pubDate>Fri, 19 Dec 2025 22:47:15 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11518</guid><comments>https://bugs.rockylinux.org/view.php?id=11518#bugnotes</comments></item><item><title>0011485: The errata page product dropdown missing RockyLinux10</title><author></author><link>https://bugs.rockylinux.org/view.php?id=11485</link><description><![CDATA[In this page: &lt;a href=&quot;https://errata.rockylinux.org/&quot; rel=&quot;noopener&quot;&gt;https://errata.rockylinux.org/&lt;/a&gt; the product dropdown selector is missing Rocky Linux 10 option even though there are errata shown for this version.]]></description><category>General</category><pubDate>Thu, 18 Dec 2025 15:44:02 +0000</pubDate><guid>https://bugs.rockylinux.org/view.php?id=11485</guid><comments>https://bugs.rockylinux.org/view.php?id=11485#bugnotes</comments></item></channel></rss>
