Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
OL 9 must clear SLUB/SLAB objects to prevent use-after-free attacks.
Description
Discussion Text
Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can be either hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.
Poisoning writes an arbitrary value to freed pages, so any modification or reference to that page after being freed or before being initialized will be detected and prevented. This prevents many types of use-after-free vulnerabilities at little performance cost. Also prevents leak of data and detection of corrupted memory.
SLAB objects are blocks of physically contiguous memory. SLUB is the unqueued SLAB allocator.
Satisfies: SRG-OS-000433-GPOS-00192, SRG-OS-000134-GPOS-00068
Poisoning writes an arbitrary value to freed pages, so any modification or reference to that page after being freed or before being initialized will be detected and prevented. This prevents many types of use-after-free vulnerabilities at little performance cost. Also prevents leak of data and detection of corrupted memory.
SLAB objects are blocks of physically contiguous memory. SLUB is the unqueued SLAB allocator.
Satisfies: SRG-OS-000433-GPOS-00192, SRG-OS-000134-GPOS-00068
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.