Re: [PATCH] libsepol: Check that a module does not have any commons when validating

On Wed, Aug 12, 2026 at 4:03 PM James Carter <[email protected]> wrote:
>
> Since a common cannot be declared in a module and cannot be
> required, there should not be any commons in a policy module. But
> a maliciously crafted policy could add one which could cause
> problems when processing the module.
>
> Check that a module does not contain any commons when validating
> the module after reading it in and quit with an error if it does.
>
> Signed-off-by: James Carter <[email protected]>

Acked-by: Stephen Smalley <[email protected]>

and merged.