ipv4: fib: Don't ignore error route in local/main tables.
- 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
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- 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
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: Don't ignore error route in local/main tables. When CONFIG_IP_MULTIPLE_TABLES is enabled but no rule is added, fib_lookup() performs route lookup directly on two tables. Since the first lookup does not properly bail out, the result of an error route in the merged local/main table could be overwritten by another route in the default table: unshare -n ip link set lo up ip route add 192.168.0.0/24 dev lo table 253 ip route add unreachable 192.168.0.0/24 ip route get 192.168.0.1 192.168.0.1 dev lo table default uid 0 cache <local> Once a random rule is added, the error route is respected: ip rule add table 0 ip rule del table 0 ip route get 192.168.0.1 RTNETLINK answers: No route to host Let's fix the inconsistent behaviour.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in a29e95fbc51e8a1b932773fd0e259b2080881443; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in 5ae18d87a45698e8244d0fcba64c658c35a7dd3d; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in 9127589aabdee588278e8d0d0bd3709a760a92c8; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in 49eaf1403201357762d745a35882fb734107d763; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in fd25996f57a95d56bc568c89b4921edcf334b7d8; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in 828fad4fd418bcdb9f5d66fec0d184c52a85ec31; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in a668fa160247d7bbe921548cb845f607b8b9305f; From f4530fa574df4d833506c53697ed1daa0d390bf4 · fixed in b72f0db64205d9ce462038ba995d5d31eff32dc1
- Linux Linux
3.6
- KernelLinux
From 3.6.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/a29e95fbc51e8a1b932773fd0e259b2080881443
- stable/c/5ae18d87a45698e8244d0fcba64c658c35a7dd3d
- stable/c/9127589aabdee588278e8d0d0bd3709a760a92c8
- stable/c/49eaf1403201357762d745a35882fb734107d763
- stable/c/fd25996f57a95d56bc568c89b4921edcf334b7d8
- stable/c/828fad4fd418bcdb9f5d66fec0d184c52a85ec31
- stable/c/a668fa160247d7bbe921548cb845f607b8b9305f
- stable/c/b72f0db64205d9ce462038ba995d5d31eff32dc1