Safeguard
Vulnerability Analysis•

CVE-2021-33631: Medium Integer Overflow in openEuler Kernel

CVE-2021-33631 is an integer overflow in the openEuler Linux kernel filesystem modules. Update to 4.19.90-2401.3 or 5.10.0-183.0.0 or later.

Safeguard Security Team
3 min read

CVE-2021-33631 is a medium severity (CVSS 5.5) integer overflow in the filesystem code of the openEuler Linux kernel that a local user can use to cause denial of service. The NVD record lists affected ranges and fixed builds: 4.19.90-2401.3 for the 4.19 line and 5.10.0-183.0.0 for the 5.10 line.

What's affected

  • openEuler kernel from 4.19.90 before 4.19.90-2401.3, per the NVD record.
  • openEuler kernel from 5.10.0-60.18.0 before 5.10.0-183.0.0, per the NVD record.
  • The record gives impact as high availability, with no confidentiality or integrity effects, and a local vector with low privileges.
  • The oss-security mailing list post in the record is a forward that points to the upstream kernel commit and the NVD entry. It does not add version information.
  • KEV status: false.

How to check if you're exposed

On an openEuler host, check the running kernel and the installed package.

uname -r
rpm -q kernel

Compare the release string with the ranges above. A host is exposed when the version falls between the lower bound and the fixed build for its line. Kernel updates need a reboot to take effect, so also confirm the running kernel, not only the installed one.

What to do now

  1. Update the kernel package from your openEuler repositories to the fixed build or later.
  2. Reboot into the new kernel, and confirm with uname -r.
  3. Where a reboot is hard to schedule, plan the window now, because the issue is a local denial of service and not an urgent remote one.
  4. Limit shell access on affected hosts to people who need it.
  5. Check any container hosts and CI runners, which share the host kernel.

Why it matters

The class is CWE-190, integer overflow or wraparound. When arithmetic on a size or count exceeds what the variable can hold, it wraps to a small value, and code that trusts the result can behave wrongly. In this case the record names the filesystem modules and the effect as a high availability impact, so a local user can bring down the system.

The score is medium because only availability is affected and an account is needed. Still, on multi tenant hosts and shared build machines, one user who can crash a kernel can disrupt everyone, so schedule the update.

One practical wrinkle is distribution kernels. Vendors backport fixes and rename builds, so a version string alone does not always tell you the full story. For openEuler, use the build numbers given in the record. For other distributions, rely on that distribution advisory and not on the upstream kernel version number. Keep a record of which kernel each host runs, so the next advisory takes minutes to match.

Quick check

Is a reboot needed?

Yes. A kernel update takes effect only after booting the new kernel.

Does this affect other Linux distributions?

The record names openEuler kernels. The mailing list post notes the commits relate to stable kernel branches, so check your distribution advisory if you run another one.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.