Bug 17790 - auditctl fails to add rule with "Error sending add rule data request" as CONFIG_AUDITSYSCALL is not enabled in our kernel
Summary: auditctl fails to add rule with "Error sending add rule data request" as CONF...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-17 22:00 CET by Florian Hubold
Modified: 2018-04-19 17:52 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Florian Hubold 2016-02-17 22:00:04 CET
When trying to use auditctl under mga5 it fails like so:

$ auditctl -w /tmp
Error sending add rule data request (Invalid argument)

Seems CONFIG_AUDITSYSCALL is not enabled anymore for the newer kernels:

$ zgrep CONFIG_AUDITSYSCALL /proc/config.gz 
# CONFIG_AUDITSYSCALL is not set

kernel used:

$ uname -r
4.1.15-desktop-2.mga5
Comment 1 Florian Hubold 2016-02-17 22:00:59 CET
@Thomas: Is there any particular reason why CONFIG_AUDITSYSCALL is disabled?

CC: (none) => doktor5000
Assignee: bugsquad => tmb

Comment 3 Marja Van Waes 2016-08-26 12:48:52 CEST
Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field.

Please reassign if needed, or add kernel to the SRPM field if this is correct.

Assignee: tmb => kernel

Comment 4 Florian Hubold 2018-04-19 17:52:57 CEST
Closing this, see comment 2 and the linked bug 13487

> kernel/auditsc.c in the Linux kernel through 3.14.5, when 
> CONFIG_AUDITSYSCALL is enabled with certain syscall rules, allows local
> users to obtain potentially sensitive single-bit values from kernel memory
> or cause a denial of service (OOPS) via a large value of a syscall number.
> (CVE-2014-3917)

> As CONFIG_SYSCALL also have other potential security issues, it has been
> disabled in order to protect installed mageia systems.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.