Skip to content

tools/oxenstored: Reset quota when resetting permissions - #28

Merged
last-genius merged 1 commit into
xapi-project:mainfrom
last-genius:asv/xsa483
Apr 30, 2026
Merged

last-genius merged 1 commit into
xapi-project:mainfrom
last-genius:asv/xsa483

Conversation

@last-genius

Copy link
Copy Markdown
Contributor

The quota object contains both limits and the current node usage counts.

When a domain is torn down, the node data itself is cleaned up but the node usage counts are not. A later domain reusing the same domid can create fewer nodes before being deemed to be over quota.

Reset the count when the node permissions are cleaned up.

This is XSA-483 / CVE-2026-23556.

The quota object contains both limits and the current node usage counts.

When a domain is torn down, the node data itself is cleaned up but the node
usage counts are not.  A later domain reusing the same domid can create fewer
nodes before being deemed to be over quota.

Reset the count when the node permissions are cleaned up.

This is XSA-483 / CVE-2026-23556.

Signed-off-by: Andrii Sultanov <andriy.sultanov@vates.tech>
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
@last-genius

Copy link
Copy Markdown
Contributor Author

I've used the patch posted as part of the XSA here: https://xenbits.xen.org/xsa/xsa483-xapi.patch

@lindig

lindig commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

A later domain reusing the same domid can create fewer nodes before being deemed to be over quota.

That's a rare case because a domid would need to warp around? If and how that happens is outside the control of this code, though.

@last-genius
last-genius merged commit 92f43a4 into xapi-project:main Apr 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants