octeontx2-af: Workaround SQM/PSE stalls by disabling sticky
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Workaround SQM/PSE stalls by disabling sticky NIX SQ manager sticky mode is known to cause stalls when multiple SQs share an SMQ and transmit concurrently. Additionally, PSE may deadlock on transitions between sticky and non-sticky transmissions. There is also a credit drop issue observed when certain condition clocks are gated. work around these hardware errata by: • Disabling SQM sticky operation: • Clear TM6 (bit 15) • Clear TM11 (bit 14) • Disabling sticky → non-sticky transition path that can deadlock PSE: • Clear TM5 (bit 23) • Preventing credit drops by keeping the control-flow clock enabled: • Set TM9 (bit 21) These changes are applied via NIX_AF_SQM_DBG_CTL_STATUS. With this configuration the SQM/PSE maintain forward progress under load without credit loss, at the cost of disabling sticky optimizations.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.5
References 8
git.kernel.org
- stable/c/9a3fd301329474f449e75f86d8a4f6b9c603fd6c
- stable/c/d0b3c8a80336029d9356f429151eb27922d80a3c
- stable/c/36cc5a5e0178d5fb79e04173b8aa623b0108819a
- stable/c/d9b549b6951ba178ec14339a031cae65f4e43fe1
- stable/c/cec2ceb35ce7bc874c43812bb39200d6cf691b87
- stable/c/8052d0587fb14b85539c3a14a226586c0c3d6b4c
- stable/c/b7eba260a34e854e2487b8363c11976f082df00d
- stable/c/70e9a5760abfb6338d63994d4de6b0778ec795d6